| Name |
Type |
Description |
Notes |
| access_token_encrypted_response_algorithm |
AccessTokenKeyEncryptionAlgorithm |
|
[optional] |
| audiences |
List[str] |
The recipients that the tokens are intended for. This becomes the `aud` claim in an access token. Okta currently supports only one audience. |
[optional] |
| created |
datetime |
|
[optional] [readonly] |
| credentials |
AuthorizationServerCredentials |
|
[optional] |
| description |
str |
The description of the custom authorization server |
[optional] |
| id |
str |
The ID of the custom authorization server |
[optional] [readonly] |
| issuer |
str |
The complete URL for the custom authorization server. This becomes the `iss` claim in an access token. |
[optional] |
| issuer_mode |
str |
Indicates which value is specified in the issuer of the tokens that a custom authorization server returns: the Okta org domain URL or a custom domain URL. `issuerMode` is visible if you have a custom URL domain configured or the Dynamic Issuer Mode feature enabled. If you have a custom URL domain configured, you can set a custom domain URL in a custom authorization server, and this property is returned in the appropriate responses. When set to `ORG_URL`, then in responses, `issuer` is the Okta org domain URL: `https://${yourOktaDomain}`. When set to `CUSTOM_URL`, then in responses, `issuer` is the custom domain URL configured in the administration user interface. When set to `DYNAMIC`, then in responses, `issuer` is the custom domain URL if the OAuth 2.0 request was sent to the custom domain, or is the Okta org's domain URL if the OAuth 2.0 request was sent to the original Okta org domain. After you configure a custom URL domain, all new custom authorization servers use `CUSTOM_URL` by default. If the Dynamic Issuer Mode feature is enabled, then all new custom authorization servers use `DYNAMIC` by default. All existing custom authorization servers continue to use the original value until they're changed using the Admin Console or the API. This way, existing integrations with the client and resource server continue to work after the feature is enabled. |
[optional] |
| jwks |
ResourceServerJsonWebKeys |
|
[optional] |
| jwks_uri |
str |
<x-lifecycle-container><x-lifecycle class="ea"></x-lifecycle></x-lifecycle-container>URL string that references a JSON Web Key Set for encrypting JWTs minted by the custom authorization server |
[optional] |
| last_updated |
datetime |
|
[optional] [readonly] |
| name |
str |
The name of the custom authorization server |
[optional] |
| status |
LifecycleStatus |
|
[optional] |
| links |
AuthServerLinks |
|
[optional] |
from okta.models.authorization_server import AuthorizationServer
# TODO update the JSON string below
json = "{}"
# create an instance of AuthorizationServer from a JSON string
authorization_server_instance = AuthorizationServer.from_json(json)
# print the JSON string representation of the object
print(AuthorizationServer.to_json())
# convert the object into a dict
authorization_server_dict = authorization_server_instance.to_dict()
# create an instance of AuthorizationServer from a dict
authorization_server_from_dict = AuthorizationServer.from_dict(authorization_server_dict)[Back to Model list] [Back to API list] [Back to README]