Skip to main content

Authentication

Kreya centralizes authentication management. Often, you only need a few different "authentication configurations" in your projects.

You can add, edit and delete authentication configurations via Project → Authentications.

Supported authentication types​

Kreya supports a range of authentication types out of the box. The authentication values are automatically transmitted in the correct format.

Basic authentication​

To add a basic authentication configuration, choose the type Basic, enter your username and password, then click Save.

Windows authentication Pro / Enterprise​

To use Windows (or any other Kerberos- or NTLM-based) authentication, create a new authentication configuration with the type System credentials (Kerberos/NTLM). Kreya uses the information of the currently logged in user to authenticate to the API.

OAuth2 / OpenID-Connect​

To add an authentication configuration for OAuth2 or OpenID-Connect, choose the type OAuth2 / OpenID-Connect. Enter the required values. Note that depending on your authentication provider and settings, not all fields need to be filled in.

Static authentication values​

Select the Static value type if your authentication value changes infrequently, such as an API key. This value will be sent as-is in the HTTP Authorization header.

Google Service Account​

The Google Service Account type allows you to access Google APIs. Simply provide a JSON key file and a scope.

AWS Signature v4​

The AWS Signature v4 type is a protocol for authenticating inbound API requests to AWS services.

Templating​

You can use templating in authentications like nearly everywhere else. This will save you a lot of time, for example when you have different passwords for each environment.

Storing sensitive information​

Values entered in authentication configurations (such as Basic authentication passwords) are stored in plain-text in the Kreya project. If you share your project, you may want to extract sensitive information. Use the Environment feature and store sensitive information in User specific data. While this still stores your sensitive data in plain text, it will be stored outside of the Kreya project and thus won't be shared.

Using authentication configurations​

To reference an authentication configuration from an operation, simply click the Auth tab and select your desired authentication configuration. Kreya now adds the correct authentication value to the request.