[{"label":"Latest (v1.0)","version":"latest"}]


The request body to update organization OAuth Application.


description Required

The description of the organization OAuth Application (client).

array of string
grantTypes Required

The OAuth grant types. Customer organizations support the following grant types: authorization_code, refresh_token, and client_credentials. Service organizations additionally support the following grant types: audience_exchange, client_delegate, and context_switch.

displayName Required

The organization OAuth Application display name.
The value must be alphanumerical and can contain the following symbols -_.`’:@&, and space. International characters are allowed.

integer as int32
accessTokenTTL Optional

The organization OAuth Application access token time to live in seconds.

array of string
allowedOrgs Optional

Allowed Organizations.
Can be used to restrict the client to sub-set of organizations.
The value is a list of organizations IDs, in which users may login using this client. If value is not presented in the request (null value) the client will not be restricted.
1. This option is available only for service organizations. Consumer organizations cannot pass this value since the client is restricted only to it’s managed organization, which cannot be changed.
2. It is not possible to update an organization/s restricted client to be a regular client.
3. The ‘allowedOrgs’ is ignored during client_credentials flow.
4. If an organization is deleted, its references in allowedOrgs are deleted eventually. ‘allowedOrgs’ may become empty if an organization gets deleted, which means users cannot login to any organization using this client. The ‘allowedOrgs’ will be ignored during client_credentials flow.

allowedScopes Optional

The allowed general, organization and service scopes of access.

crossOrgAccessClaimsSupported Optional

Indicates whether the oauth client supports cross-org roles.

array of string
allowedActorsClientDelegate Optional

The List of other OAuth App identifiers who can act on behalf of this OAuth App

array of string
allowedActorsAudienceExchange Optional

The List of other OAuth App identifiers who can exchange id token from this OAuth App

forcePkce Optional

When set to true, the flag mandates the use of PKCE when doing an authorization_code flow (i.e., the request will fail if PKCE is not used).

array of string
additionalAttributeMasks Optional

Additional attribute masks. Refer to GAZ docs.

groupDomainAppendedInIDToken Optional

Temporary flag used to request de-dup of domain name in ID token by setting value to ‘false’.

isHidden Optional

When set to true, this OAuth Application will not be displayed on the UI.

integer as int32
maxCharactersInAccessToken Optional

Limit the number of text characters that will be put in the access token. If the resulting access token would exceed this value, an overflow behavior will be triggered. If overflow is triggered, the returned access token will contain a claim ‘ovc’ that lists the claims which have overflowed. For example ‘ovc’ : [‘perms’, ‘authorization_details’]. When overflow is triggered, the token will also contain an ‘ovl’ claim containing a URL which can be can be used to expand the access token and return the claims as JSON. For example ‘ovl’: ‘https://gaz.csp-vidm-prod.com/api/check_access_token' When ‘maxCharactersInAccessToken’ is not set (the default), a system defined value will be used. Currently this value is 3415 characters, or about 5KB. The purpose of this behavior is to help ensure that the request headers containing the JWT access token do not become arbitrarily large. Your system must be able to handle a token that contains ‘ovc’ and ‘ovl’ claims.

integer as int32
maxGroupsInIdToken Optional

The maximum number of groups allowed in the ID token. In case the user is a member in more groups than the value specified in the OAuth client, a URL will be attached to the ID token under the ‘ovl’ claim.

ownerOnlySecretRotation Optional

When set to ’true’, the client is not allowed to rotate its own secret. Client rotation will be enabled for organization owner/service owner only using client rotation management APIs. By default, client is enabled to self-rotate its secret.

array of string
postLogoutRedirectUris Optional

Post logout redirect URIs, can be used by a service as a custom redirect destination after logout. For e.g., the service login/home page. Relevant only for authorization_code grant type. The PATCH operation will override the entire existing list.

array of string
redirectUris Optional

The organization OAuth Application redirect URIs.. Relevant only for authorization_code grant type

integer as int32
refreshTokenTTL Optional

The organization OAuth Application refresh token time to live in seconds.

string as (?=.{8,})(?=.*[a-z])(?=.*[A-Z])(?=.*[0-9])(?=.*[!@#$%^&*()_+=\[\]-{|}',./:;<>?`~]).*
secret Optional

The organization OAuth Application secret
Changing the client secret via the client management APIs will reset existing secret rotation (meaning, the provided secret in the management APIs will be the only valid secret).

integer as int32
secretRotationExpirationInSeconds Optional

The secret rotation expiration in seconds. The old OAuth Application secret will expire after it. If not specified, the default expiration time is 48 hours.
Optionally override the default number of seconds before a new OAuth Application secret will automatically be rotated when using the OAuth Application secret rotation APIs.

serviceDefinitionId Optional

Service definition ID of the service using this authorization code webapp. Required in production for tracking purposes.

useCspIssuerUrl Optional

Temporary flag used to request issuer URL to be set to CSP URL so that it is OIDC compliant (Default false, but will be changed to true after deprecation cycle).

JSON Example

	"description": "string",
	"displayName": "string",
	"grantTypes": [
[{"label":"Latest (v1.0)","version":"latest"}]
Parameter To

Update Organization OAuth Application By Organization ID And Application ID


Was this page helpful?