Auth Bearer Service Configuration
The auth Service Family
Infinite Scale uses several authentication services for different use cases. All services that start with auth- are part of the authentication service family. Each member authenticates requests with different scopes.
As of now, these auth services exist |
|
|---|---|
Handles 3rd party app authentication. |
|
Handles basic authentication. |
|
Handles OIDC authentication. |
|
Handles interservice authentication when a user is impersonated. |
|
Handles interservice authentication when using service accounts. |
|
Built in OpenID Connect Identity Provider
A default Infinite Scale deployment will start a built-in OpenID Connect identity provider but can be configured to use an external one as well.
Scalability
There is no persistance or caching. The proxy caches verified auth bearer tokens. Requests will be forwarded to the identity provider. Therefore, multiple instances of the auth-bearer service can be started without further configuration. Currently, the auth registry used by the gateway service can only use a single instance of the service. To use more than one auth provider per deployment, you need to scale the gateway.
This will change over time and be documented when available.
Configuration
Environment Variables
The auth-bearer service is configured via the following environment variables. Read the Environment Variable Types documentation for important details. Column IV shows with which release the environment variable has been introduced.
404: Not Found
YAML Example
-
Note the file shown below must be renamed and placed in the correct folder according to the Configuration File Naming conventions to be effective.
-
See the Notes for Environment Variables if you want to use environment variables in the yaml file.