Default-token-issuer (Section)#
Path: /profiles/profile{id, type}/token-issuers/default-token-issuer
These settings are used to define the default Token issuers. They are needed, if no custom issuer is mapped. The default Token Procedures assume that these are available
Parameters#
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
| access-token-as-jwt | empty | optional | Indicates whether to issue the Access Token as JWT | |
| default-data-source | leafref | required | The default data-source used for token persistence | |
| use-wrapped-opaque-tokens | empty | optional | Indicates whether the default token issuers return a wrapper JWT instead of an opaque reference as the token artifact. The claims that go into this JWT can be configured using claim mappers. Note that these claims are different from the claims that go into the main token data, which are available via token introspection. This applies to all default access tokens, refresh tokens and authorization codes, with the exception of DCR Management tokens which are always reference tokens. |
Subsections#
| Name | Type | Description |
|---|---|---|
| jwt-issuer-settings | Section | None |
| use-caching-services | Section | Use the system’s default caching data source, instead of the default token data source, to store short-lived tokens. |