Credentials

Note: Permission to manage Credentials is needed to use the functionality described on this page. However, all users can use credentials when configuring modules in flows.

The Credentials library is a central repository for storing credentials needed by flow modules when accessing external services, for example username/password or API keys. Once a credential has been added to the library it can be selected in the module settings by referencing the name of the credential. In this way only the credential managers will ever see the actual data used, regular users will only access credentials by name referral. Credentials are stored encrypted in Crosser Cloud and are also delivered to and stored in the edge nodes encrypted. When configuring a module only credentials supported by that module will be available. A module can support multiple credential types.

The Credentials page lists all currently available credentials and their type. To add a new credential use the '+ Add Credential' button on the Credentials page or use the '+' button next to the credential selector in the settings UI on modules that use credentials. In the form that is opened, start by giving the credential a name. This is the name shown to users when configuring a module, so you should preferably use a name that helps the users to select the appropriate credential. Then select a type and enter the actual credential settings. There is also a description field that can be used to enter any relevant information about the credential, e.g. expiration times, endpoints supported and so on. The description can be seen by expanding the row for a credential in the table on the Credentials page.

Credential types

Crosser supports many different types of credentials, including standard types like username/password (basic), API key (bearer), Oauth and certificates, but also special credential types used by specific services. The list is expanded constantly based on the currently supported services.