Configuration
| Configuration | Description |
|---|---|
| Key store | Server keys configuration. |
| Core | Core OAuth 2.0 and OpenID Connect configuration. |
| Session store | End-user web and device sessions configuration. |
| Authorisation store | OAuth 2.0 authorisation code, access token and refresh token configuration. |
| Database, caching and clustering | Backend database, caching and clustering configuration. |
| Monitoring | Monitoring endpoint and metrics reporting (JMX, Graphite, Prometheus) configuration. |
| Tenants | Tenants registry configuration (multitenant edition only). |
| Logging | Logging of server and endpoint events configuration. |
| Claims sources | Configurations of the LDAP, HTTP endpoint (web hook) and subject session sources of OpenID claims. |
| Custom scopes for claims | Custom map for requesting OpenID claims with scope values. |
| Access token compression | List of OpenID claims to compress in self-contained (JWT-encoded) access tokens. |
| Cross-Origin Resource Sharing | Handling of cross-domain (CORS) access to the Connect2id server endpoints. |
Important
-
The Connect2id server must be restarted in order for a configuration change to take effect. This doesn’t apply to the multitenant server edition where the configurations of tenants are managed by a web API.
-
After Connect2id server startup check the logs for recorded configuration errors and security warnings.
-
Read the external configuration guide for tips how to pass Java system properties from environment variables, local files and other sources.