Skip to content

AddClientAccessTokenParams

The addClientAccessTokenParams section allows you to set some specific values ​​to be used in getting the Access Token of type 'client_credentials' for Http calls.

If this section is not filled in, the Access Token will assume the default values, which will be detailed in the following fields.

Fields

A addClientAccessTokenParam contains the following fields to be defined:

ClientIdEnvName

The name of environment variable that contains the value for client_id property. This environment variable must be mapped into the service container.

Note

If this field is not filled in, the handler will use the ClientId defined for the service in the environment variables file generated by Beatrix.

Example:

1
2
AddClientAccessTokenParams:
  ClientIdEnvName: MySettings:ServiceSource:ClientId


ClientSecretEnvName

The name of environment variable that contains the value for client_secret property. This environment variable must be mapped into the service container.

Note

If this field is not filled in, the handler will use the ClientSecret defined for the service in the environment variables file generated by Beatrix.

Example:

1
2
3
AddClientAccessTokenParams:
  ClientIdEnvName: MySettings:ServiceSource:ClientId
  ClientSecretEnvName: MySettings:ServiceSource:ClientSecret


Scopes

One or more scopes registered for the service that will perform the Http call. These scopes must match the AllowedScopes defined for the service.

This option allows you to define only those scopes that are actually part of the request context. This decreases the attack surface if the Token leaks.

Note

If this field is not filled in, the Token will be issued with all the Allowed Scopes defined for the service.

Example:

1
2
3
4
5
AddClientAccessTokenParams:
  ClientIdEnvName: MySettings:ServiceSource:ClientId
  ClientSecretEnvName: MySettings:ServiceSource:ClientSecret
  Scopes:
  - ServiceSource


Back to top