diff --git a/providers/src/okta/v00.00.00000/provider.yaml b/providers/src/okta/v00.00.00000/provider.yaml
index 0a3e300d..efb63731 100644
--- a/providers/src/okta/v00.00.00000/provider.yaml
+++ b/providers/src/okta/v00.00.00000/provider.yaml
@@ -498,8 +498,7 @@ providerServices:
version: v00.00.00000
description: okta zones API
config:
- config:
- auth:
- credentialsenvvar: OKTA_API_TOKEN
- type: api_key
- valuePrefix: 'SSWS '
+ auth:
+ credentialsenvvar: OKTA_API_TOKEN
+ type: api_key
+ valuePrefix: 'SSWS '
diff --git a/providers/src/okta/v00.00.00000/services/Org.yaml b/providers/src/okta/v00.00.00000/services/Org.yaml
index 94246171..fd43cd5c 100644
--- a/providers/src/okta/v00.00.00000/services/Org.yaml
+++ b/providers/src/okta/v00.00.00000/services/Org.yaml
@@ -495,7 +495,7 @@ paths:
- name: expand
in: query
description: >-
- Embeds the [user](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/)
+ Embeds the [user](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/)
resource if the YubiKey token is assigned to a user and `expand` is
set to `user`
schema:
@@ -1173,7 +1173,7 @@ paths:
> **Note:** This resource is deprecated. Use the [Update an Okta Support
- case](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingSupport/#tag/OrgSettingSupport/operation/updateOktaSupportCase)
+ case](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingSupport/#tag/OrgSettingSupport/operation/updateOktaSupportCase)
resource to extend Okta Support access for a support case.
> For the corresponding Okta Admin Console feature, see [Give access to
@@ -1205,7 +1205,7 @@ paths:
> **Note:** This resource is deprecated. Use the [Update an Okta Support
- case](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingSupport/#tag/OrgSettingSupport/operation/updateOktaSupportCase)
+ case](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingSupport/#tag/OrgSettingSupport/operation/updateOktaSupportCase)
resource to grant Okta Support access for a support case.
> For the corresponding Okta Admin Console feature, see [Give access to
@@ -1236,7 +1236,7 @@ paths:
> **Note:** This resource is deprecated. Use the [Update an Okta Support
- case](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingSupport/#tag/OrgSettingSupport/operation/updateOktaSupportCase)
+ case](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingSupport/#tag/OrgSettingSupport/operation/updateOktaSupportCase)
resource to revoke Okta Support access for a support case.
> For the corresponding Okta Admin Console feature, see [Give access to
@@ -1719,31 +1719,31 @@ components:
- $ref: '#/components/schemas/HrefObject'
- description: >-
Link to [extend Okta Support
- Access](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingSupport/#tag/OrgSettingSupport/operation/extendOktaSupport)
+ Access](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingSupport/#tag/OrgSettingSupport/operation/extendOktaSupport)
revoke:
allOf:
- $ref: '#/components/schemas/HrefObject'
- description: >-
Link to [revoke Okta Support
- Access](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingSupport/#tag/OrgSettingSupport/operation/revokeOktaSupport)
+ Access](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingSupport/#tag/OrgSettingSupport/operation/revokeOktaSupport)
grant:
allOf:
- $ref: '#/components/schemas/HrefObject'
- description: >-
Link to [grant Okta Support
- Access](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingSupport/#tag/OrgSettingSupport/operation/grantOktaSupport)
+ Access](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingSupport/#tag/OrgSettingSupport/operation/grantOktaSupport)
case:
allOf:
- $ref: '#/components/schemas/HrefObject'
- description: >-
Link to [update an Okta Support
- case](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingSupport/#tag/OrgSettingSupport/operation/updateOktaSupportCase)
+ case](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingSupport/#tag/OrgSettingSupport/operation/updateOktaSupportCase)
cases:
allOf:
- $ref: '#/components/schemas/HrefObject'
- description: >-
Link to [List all Okta Support
- cases](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingSupport/#tag/OrgSettingSupport/operation/listOktaSupportCases)
+ cases](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingSupport/#tag/OrgSettingSupport/operation/listOktaSupportCases)
OktaSupportCases:
type: object
properties:
@@ -1821,7 +1821,7 @@ components:
- $ref: '#/components/schemas/HrefObject'
- description: >-
Link to the [Org
- Contacts](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingContact/)
+ Contacts](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingContact/)
resource
logo:
allOf:
@@ -1832,28 +1832,28 @@ components:
- $ref: '#/components/schemas/HrefObject'
- description: >-
Link to the [Org Communication
- Settings](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingCommunication/)
+ Settings](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingCommunication/)
resource
oktaSupport:
allOf:
- $ref: '#/components/schemas/HrefObject'
- description: >-
Link to the [Org Support
- Settings](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingSupport/)
+ Settings](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingSupport/)
resource
preferences:
allOf:
- $ref: '#/components/schemas/HrefObject'
- description: >-
Link to the [Org
- Preferences](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingCustomization/#tag/OrgSettingCustomization/operation/getOrgPreferences)
+ Preferences](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingCustomization/#tag/OrgSettingCustomization/operation/getOrgPreferences)
resource
uploadLogo:
allOf:
- $ref: '#/components/schemas/HrefObject'
- description: >-
Link to the [Upload Org
- Logo](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingCustomization/#tag/OrgSettingCustomization/operation/uploadOrgLogo)
+ Logo](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingCustomization/#tag/OrgSettingCustomization/operation/uploadOrgLogo)
resource
readOnly: true
enabledPagesType:
@@ -1923,7 +1923,7 @@ components:
- $ref: '#/components/schemas/HrefObject'
- description: >-
Link to the org billing [contact type
- user](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingContact/#tag/OrgSettingContact/operation/getOrgContactUser)
+ user](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingContact/#tag/OrgSettingContact/operation/getOrgContactUser)
resource
orgTechnicalContactType:
description: Org technical contact
@@ -1947,7 +1947,7 @@ components:
- $ref: '#/components/schemas/HrefObject'
- description: >-
Link to the org technical [Contact Type
- User](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingContact/#tag/OrgSettingContact/operation/getOrgContactUser)
+ User](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/OrgSettingContact/#tag/OrgSettingContact/operation/getOrgContactUser)
resource
OrgContactType:
description: Type of contact
@@ -2046,7 +2046,7 @@ components:
allOf:
- description: >-
Activates an enrolled factor. See [Activate a
- factor](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/activateFactor).
+ factor](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/activateFactor).
- $ref: '#/components/schemas/HrefObject'
readOnly: true
LinksCancel:
@@ -2064,7 +2064,7 @@ components:
allOf:
- description: >-
Deactivates the factor. See [Unenroll a
- factor](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/unenrollFactor).
+ factor](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/unenrollFactor).
- $ref: '#/components/schemas/HrefObject'
readOnly: true
LinksEnroll:
@@ -2074,7 +2074,7 @@ components:
allOf:
- description: >-
Enrolls a supported factor. See [Enroll a
- factor](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/enrollFactor).
+ factor](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/enrollFactor).
- $ref: '#/components/schemas/HrefObject'
readOnly: true
LinksFactor:
@@ -2113,7 +2113,7 @@ components:
- description: >-
Lists all supported security questions. See [List all supported
security
- questions](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/listSupportedSecurityQuestions).
+ questions](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/listSupportedSecurityQuestions).
- $ref: '#/components/schemas/HrefObject'
readOnly: true
LinksResend:
@@ -2123,7 +2123,7 @@ components:
allOf:
- description: >-
Resends the factor enrollment challenge. See [Resend a factor
- enrollment](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/resendEnrollFactor).
+ enrollment](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/resendEnrollFactor).
- $ref: '#/components/schemas/HrefObject'
readOnly: true
LinksSend:
@@ -2164,7 +2164,7 @@ components:
allOf:
- description: >-
Verifies the factor resource. See [Verify a
- factor](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/verifyFactor).
+ factor](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/verifyFactor).
- $ref: '#/components/schemas/HrefObject'
readOnly: true
HrefObjectRevokeAerialConsent:
diff --git a/providers/src/okta/v00.00.00000/services/apps.yaml b/providers/src/okta/v00.00.00000/services/apps.yaml
index cabb9843..04682164 100644
--- a/providers/src/okta/v00.00.00000/services/apps.yaml
+++ b/providers/src/okta/v00.00.00000/services/apps.yaml
@@ -17,7 +17,7 @@ paths:
> **Note:** To list all of a member's assigned app links, use the [List
all assigned app links endpoint in the User Resources
- API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserResources/#tag/UserResources/operation/listAppLinks).
+ API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserResources/#tag/UserResources/operation/listAppLinks).
operationId: listApplications
parameters:
- name: q
@@ -123,11 +123,11 @@ paths:
* OIN app instances have prescribed `name` (key app definition) and
`signOnMode` options. See the [OIN
- schemas](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/schema/GoogleApplication)
+ schemas](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/schema/GoogleApplication)
for the request body.
* For custom app instances, select the
- [signOnMode](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/createApplication!path=0/signOnMode&t=request)
+ [signOnMode](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/createApplication!path=0/signOnMode&t=request)
that pertains to your app and specify the required parameters in the
request body.
operationId: createApplication
@@ -219,7 +219,7 @@ paths:
in: query
description: >-
An optional query parameter to return the specified [Application
- User](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/) in
+ User](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/) in
the `_embedded` property.
Valid value: `expand=user/{userId}`
@@ -870,14 +870,14 @@ paths:
> **Note:** This API doesn't allow you to add a key if the existing key
doesn't have a `kid`. This is also consistent with how the [Dynamic
Client Registration](/openapi/okta-oauth/oauth/tag/Client/) or
- [Applications](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/)
+ [Applications](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/)
APIs behave, as they don't allow the creation of multiple keys without
`kids`. Use the [Replace an
- Application](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/replaceApplication)
+ Application](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/replaceApplication)
or the [Replace a Client
Application](/openapi/okta-oauth/oauth/tag/Client/#tag/Client/operation/replaceClient)
operation to update the JWKS or [Delete an OAuth 2.0 Client JSON Web
- Key](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationSSOPublicKeys/#tag/ApplicationSSOPublicKeys/operation/deletejwk)
+ Key](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationSSOPublicKeys/#tag/ApplicationSSOPublicKeys/operation/deletejwk)
and re-add the key with a `kid`.
operationId: addJwk
requestBody:
@@ -1161,13 +1161,13 @@ paths:
> **Note:** To update an Application with the newly generated key
credential, use the [Replace an
- Application](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/replaceApplication)
+ Application](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/replaceApplication)
request with the new
- [credentials.signing.kid](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/replaceApplication!path=4/credentials/signing/kid&t=request)
+ [credentials.signing.kid](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/replaceApplication!path=4/credentials/signing/kid&t=request)
value in the request body. You can provide just the [Signing Credential
- object](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/replaceApplication!path=4/credentials/signing&t=request)
+ object](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/replaceApplication!path=4/credentials/signing&t=request)
instead of the entire [Application Credential
- object](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/replaceApplication!path=4/credentials&t=request).
+ object](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/replaceApplication!path=4/credentials&t=request).
operationId: generateApplicationKey
parameters:
- name: validityYears
@@ -1347,7 +1347,7 @@ paths:
you attempt to create more than two Secret objects.
> **Note:** This API lets you bring your own secret. If
- [token_endpoint_auth_method](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/createApplication!path=4/credentials/oauthClient/token_endpoint_auth_method&t=request)
+ [token_endpoint_auth_method](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/createApplication!path=4/credentials/oauthClient/token_endpoint_auth_method&t=request)
of the app is `client_secret_jwt`, then the minimum length of
`client_secret` is 32 characters. If no secret is specified in the
request, Okta adds a new system-generated secret.
@@ -1772,7 +1772,7 @@ paths:
for the app.
> To set up provisioning, see [Update the default provisioning
- connection](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationConnections/#tag/ApplicationConnections/operation/updateDefaultProvisioningConnectionForApplication).
+ connection](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationConnections/#tag/ApplicationConnections/operation/updateDefaultProvisioningConnectionForApplication).
operationId: listFeaturesForApplication
responses:
'200':
@@ -2517,7 +2517,7 @@ paths:
This filter only supports the `startsWith` operation that matches
the `q` string against the beginning of the [group
- name](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/listGroups!c=200&path=profile/name&t=response).
+ name](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/listGroups!c=200&path=profile/name&t=response).
schema:
type: string
example: test
@@ -2598,13 +2598,13 @@ paths:
summary: Assign an application group
description: >-
Assigns a
- [Group](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/)
+ [Group](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/)
to an app, which in turn assigns the app to each
- [User](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/)
+ [User](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/)
that belongs to the group.
The resulting application user
- [scope](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/#tag/ApplicationUsers/operation/listApplicationUsers!c=200&path=scope&t=response)
+ [scope](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/#tag/ApplicationUsers/operation/listApplicationUsers!c=200&path=scope&t=response)
is `GROUP` since the assignment was from the group membership.
operationId: assignGroupToApplication
x-codegen-request-body-name: applicationGroupAssignment
@@ -2851,7 +2851,7 @@ paths:
summary: Assign an authentication policy
description: >-
Assigns an app to an [authentication
- policy](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Policy/), identified by
+ policy](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Policy/), identified by
`policyId`.
If the app was previously assigned to another policy, this operation
@@ -3394,7 +3394,7 @@ components:
Enabled app features
> **Note:** See [Application
- Features](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationFeatures/)
+ Features](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationFeatures/)
for app provisioning features.
readOnly: true
items:
@@ -3590,14 +3590,14 @@ components:
Language](https://datatracker.ietf.org/doc/html/draft-kelly-json-hal-06)
specification. If the `expand=user/{userId}` query parameter is
specified, then the assigned [Application
- User](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/) is
+ User](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/) is
embedded.
properties:
user:
type: object
description: >-
The specified [Application
- User](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/)
+ User](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/)
assigned to the app
additionalProperties:
type: object
@@ -4318,7 +4318,7 @@ components:
type: string
description: >-
ID of the
- [group](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/)
+ [group](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/)
readOnly: true
example: 00g4hb1HChfUriNgW0g4
lastUpdated:
@@ -4331,7 +4331,7 @@ components:
Priority assigned to the group. If an app has more than one group
assigned to the same user, then the group with the higher priority
has its profile applied to the [application
- user](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/).
+ user](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/).
If a priority value isn't specified, then the next highest priority
is assigned by default.
@@ -4352,7 +4352,7 @@ components:
specification.
If the `expand=group` query parameter is specified, then the
- [group](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/)
+ [group](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/)
object is embedded.
If the `expand=metadata` query parameter is specified, then the
@@ -5255,12 +5255,12 @@ components:
GroupAssignmentProfile:
description: >-
Specifies the profile properties applied to [application
- users](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/)
+ users](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/)
that are assigned to the app through group membership.
Some reference properties are imported from the target app and can't be
configured. See
- [profile](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#tag/User/operation/getUser!c=200&path=profile&t=response).
+ [profile](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#tag/User/operation/getUser!c=200&path=profile&t=response).
additionalProperties: true
type: object
HrefObjectAppLink:
@@ -5329,9 +5329,9 @@ components:
Specifies a user's credentials for the app.
This parameter can be omitted for apps with [sign-on
- mode](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/getApplication!c=200&path=0/signOnMode&t=response)
+ mode](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/getApplication!c=200&path=0/signOnMode&t=response)
(`signOnMode`) or [authentication
- schemes](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/getApplication!c=200&path=0/credentials/scheme&t=response)
+ schemes](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/getApplication!c=200&path=0/credentials/scheme&t=response)
(`credentials.scheme`) that don't require credentials.
type: object
properties:
@@ -5344,13 +5344,13 @@ components:
> **Note:** The
- [userNameTemplate](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/createApplication!path=0/credentials/userNameTemplate&t=request)
+ [userNameTemplate](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/createApplication!path=0/credentials/userNameTemplate&t=request)
in the application object defines the default username generated
when a user is assigned to that app.
> If you attempt to assign a username or password to an app with an
incompatible [authentication
- scheme](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/createApplication!path=0/credentials/scheme&t=request),
+ scheme](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/createApplication!path=0/credentials/scheme&t=request),
the following error is returned:
> "Credentials should not be set on this resource based on the
@@ -5369,7 +5369,7 @@ components:
target app and can't be configured.
See
- [profile](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#tag/User/operation/getUser!c=200&path=profile&t=response).
+ [profile](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#tag/User/operation/getUser!c=200&path=profile&t=response).
additionalProperties: true
type: object
AppUserStatus:
@@ -5501,7 +5501,7 @@ components:
conditional updates. As long as you're the only user updating the the
user profile, Okta recommends you fetch the most recent profile with
[Retrieve an Application
- User](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/#tag/ApplicationUsers/operation/getApplicationUser),
+ User](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/#tag/ApplicationUsers/operation/getApplicationUser),
apply your profile update, and then `POST` back the updated profile.
type: object
properties:
@@ -5575,7 +5575,7 @@ components:
- $ref: '#/components/schemas/HrefObject'
- description: >-
Link to the [Application
- Groups](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationGroups/#tag/ApplicationGroups/operation/listApplicationGroupAssignments)
+ Groups](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationGroups/#tag/ApplicationGroups/operation/listApplicationGroupAssignments)
resource
HelpLink:
allOf:
@@ -5586,7 +5586,7 @@ components:
- $ref: '#/components/schemas/HrefObject'
- description: >-
Link to the [SAML
- metadata](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationSSO/#tag/ApplicationSSO/operation/previewSAMLmetadataForApplication)
+ metadata](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationSSO/#tag/ApplicationSSO/operation/previewSAMLmetadataForApplication)
for SSO
HrefObjectSelfLink:
allOf:
@@ -5597,7 +5597,7 @@ components:
- $ref: '#/components/schemas/HrefObject'
- description: >-
Link to the [Application
- Users](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/#tag/ApplicationUsers/operation/listApplicationUsers)
+ Users](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/#tag/ApplicationUsers/operation/listApplicationUsers)
resource
ProvisioningConnectionAuthScheme:
description: Defines the method of authentication
@@ -5880,7 +5880,7 @@ components:
AUTO: >-
Okta manages key rotation for the provisioning connection. Use the
[Retrieve a JWKS for the default provisioning
- connection](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationConnections/#tag/ApplicationConnections/operation/getUserProvisioningConnectionJWKS)
+ connection](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationConnections/#tag/ApplicationConnections/operation/getUserProvisioningConnectionJWKS)
endpoint for the latest key credentials.
MANUAL: >-
You need to rotate the keys for your provisioning connection manually
@@ -6044,7 +6044,7 @@ components:
eq "{userId}"` filter query for the same user.
Returns the assigned [application
- user](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/) in the
+ user](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/) in the
`_embedded` property.
schema:
type: string
@@ -6169,7 +6169,7 @@ components:
in: query
description: >-
An optional query parameter to return the corresponding assigned
- [group](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/)
+ [group](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/)
or
the group assignment metadata details in the `_embedded` property.
@@ -6196,7 +6196,7 @@ components:
in: query
description: >-
An optional query parameter to return the corresponding assigned
- [group](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/)
+ [group](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/)
or
the group assignment metadata details in the `_embedded` property.
@@ -6286,7 +6286,7 @@ components:
in: query
description: >-
An optional query parameter to return the corresponding
- [User](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/) object in the
+ [User](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/) object in the
`_embedded` property.
Valid value: `user`
diff --git a/providers/src/okta/v00.00.00000/services/authorizationservers.yaml b/providers/src/okta/v00.00.00000/services/authorizationservers.yaml
index d890bb47..c70a9844 100644
--- a/providers/src/okta/v00.00.00000/services/authorizationservers.yaml
+++ b/providers/src/okta/v00.00.00000/services/authorizationservers.yaml
@@ -556,7 +556,7 @@ paths:
> **Note:** To list a specific user's client resources for which they
have tokens or grants, use the [List all clients endpoint in the User
Resources
- API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserResources/#tag/UserResources/operation/listUserClients).
+ API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserResources/#tag/UserResources/operation/listUserClients).
operationId: listOAuth2ClientsForAuthorizationServer
responses:
'200':
@@ -1482,10 +1482,10 @@ paths:
> **Note:** This API doesn't allow you to add a key if the existing key
doesn't have a `kid`. Use the [Replace an Authorization
- Server](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/AuthorizationServer/#tag/AuthorizationServer/operation/replaceAuthorizationServer)
+ Server](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/AuthorizationServer/#tag/AuthorizationServer/operation/replaceAuthorizationServer)
operation to update the JWKS or [Delete a Custom Authorization Server
Public JSON Web
- Key](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/OAuth2ResourceServerCredentialsKeys/#tag/OAuth2ResourceServerCredentialsKeys/operation/deleteOAuth2ResourceServerJsonWebKey)
+ Key](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/OAuth2ResourceServerCredentialsKeys/#tag/OAuth2ResourceServerCredentialsKeys/operation/deleteOAuth2ResourceServerJsonWebKey)
and re-add the key with a `kid`.
> **Note:** This API doesn't allow you to add a key with an ACTIVE
diff --git a/providers/src/okta/v00.00.00000/services/devices.yaml b/providers/src/okta/v00.00.00000/services/devices.yaml
index eb514baf..d1f45a65 100644
--- a/providers/src/okta/v00.00.00000/services/devices.yaml
+++ b/providers/src/okta/v00.00.00000/services/devices.yaml
@@ -13,7 +13,7 @@ paths:
>**Note:** To list all devices enrolled by a user, use the [List all
devices endpoint in the User Resources
- API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserResources/#tag/UserResources/operation/listUserDevices).
+ API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserResources/#tag/UserResources/operation/listUserDevices).
You can return a subset of devices that match a supported search
@@ -190,7 +190,7 @@ paths:
Deletes (permanently) a device by `deviceId` if it has a status of
`DEACTIVATED`. You can transition the device to `DEACTIVATED` status
using the [Deactivate a
- Device](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Device/#tag/Device/operation/deactivateDevice)
+ Device](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Device/#tag/Device/operation/deactivateDevice)
endpoint.
This request is destructive and deletes all of the profile data related
@@ -663,7 +663,7 @@ components:
type: string
description: >-
The ID of the realm in which the user is residing. See
- [Realms](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Realm/).
+ [Realms](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Realm/).
example: guo1bfiNtSnZYILxO0g4
readOnly: true
status:
@@ -690,7 +690,7 @@ components:
description: >-
The user type that determines the schema for the user's profile. The
`type` property is a map that identifies the [User
- Types](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserType/#tag/UserType).
+ Types](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserType/#tag/UserType).
Currently it contains a single element, `id`. It can be specified
@@ -728,9 +728,9 @@ components:
For a collection of users, the links object contains only the `self`
link. Operations that return a collection of users include [List all
- users](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#tag/User/operation/listUsers)
+ users](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#tag/User/operation/listUsers)
and [List all group member
- users](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/listGroupUsers).
+ users](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/listGroupUsers).
allOf:
- $ref: '#/components/schemas/LinksSelf'
- type: object
@@ -908,7 +908,7 @@ components:
[pattern](https://developer.okta.com/docs/reference/api/schemas/#login-pattern-validation)
for `login`. You can use the Profile Editor in the Admin Console or the
[Schemas
- API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UISchema/#tag/UISchema)
+ API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UISchema/#tag/UISchema)
to make schema modifications.
@@ -916,7 +916,7 @@ components:
the custom property to the user profile schema before you reference it.
You can use the Profile Editor in the Admin Console or the [Schemas
- API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UISchema/#tag/UISchema)
+ API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UISchema/#tag/UISchema)
to manage schema extensions.
@@ -1023,7 +1023,7 @@ components:
that include @-signs. (By default, usernames must be formatted as
email addresses and thus always include @-signs. You can remove that
restriction using either the Admin Console or the [Schemas
- API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Schema/).
+ API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Schema/).
Users can sign in with their non-qualified short name (for example:
isaac.brock with username isaac.brock@example.com) as long as the
short name is still unique within the organization.
@@ -1264,7 +1264,7 @@ components:
from some other store. Okta supports the BCRYPT, SHA-512, SHA-256,
SHA-1, MD5, and PBKDF2 hash functions for password import.
A hashed password may be specified in a password object when creating or updating a user, but not for other operations.
- See the [Create user with imported hashed password](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-with-imported-hashed-password) description. When you update a user with a hashed password, the user must be in the `STAGED` status.
+ See the [Create user with imported hashed password](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-with-imported-hashed-password) description. When you update a user with a hashed password, the user must be in the `STAGED` status.
type: object
properties:
algorithm:
@@ -1322,7 +1322,7 @@ components:
PasswordCredentialHook:
description: >-
Specify a [password import inline
- hook](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/InlineHook/#tag/InlineHook/operation/createPasswordImportInlineHook)
+ hook](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/InlineHook/#tag/InlineHook/operation/createPasswordImportInlineHook)
to trigger verification of the user's password the first time the user
signs in. This allows an existing password to be imported into Okta
directly from some other store.
diff --git a/providers/src/okta/v00.00.00000/services/eventhooks.yaml b/providers/src/okta/v00.00.00000/services/eventhooks.yaml
index 95a3ef13..f459fdd5 100644
--- a/providers/src/okta/v00.00.00000/services/eventhooks.yaml
+++ b/providers/src/okta/v00.00.00000/services/eventhooks.yaml
@@ -516,7 +516,7 @@ components:
> **Note:** Event hook filters is a [self-service Early Access
- (EA)](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/guides/release-lifecycle/#early-access-ea)
+ (EA)](https://developer.okta.com/docs/api/openapi/okta-management/guides/release-lifecycle/#early-access-ea)
to enable.
If you want to disable this feature, it's recommended to first remove
diff --git a/providers/src/okta/v00.00.00000/services/groups.yaml b/providers/src/okta/v00.00.00000/services/groups.yaml
index dd627ea9..a66eb4c3 100644
--- a/providers/src/okta/v00.00.00000/services/groups.yaml
+++ b/providers/src/okta/v00.00.00000/services/groups.yaml
@@ -13,11 +13,11 @@ paths:
> **Note:** To list all groups belonging to a member, use the [List all
groups endpoint in the User Resources
- API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserResources/#tag/UserResources/operation/listUserGroups).
+ API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserResources/#tag/UserResources/operation/listUserGroups).
The number of groups returned depends on the specified
- [`limit`](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/listGroups!in=query&path=limit&t=request),
+ [`limit`](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/listGroups!in=query&path=limit&t=request),
if you have a search, filter, and/or query parameter set, and if that
parameter is not null. We recommend using a limit less than or equal to
200.
@@ -58,7 +58,7 @@ paths:
`lastMembershipUpdated`, `lastUpdated`, and `type`.
* The
- [source](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/listGroups!c=200&path=_links/source&t=response)
+ [source](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/listGroups!c=200&path=_links/source&t=response)
of groups with type of `APP_GROUP`, accessed as `source.id`.
@@ -193,7 +193,7 @@ paths:
If specified, additional metadata is included in the response.
Possible values are `stats` and `app`. This additional metadata is
listed in the
- [`_embedded`](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/addGroup!c=200&path=_embedded&t=response)
+ [`_embedded`](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/addGroup!c=200&path=_embedded&t=response)
property of the response.
@@ -672,7 +672,7 @@ paths:
summary: List all assigned apps
description: >-
Lists all apps that are assigned to a group. See [Application Groups
- API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationGroups/).
+ API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationGroups/).
operationId: listAssignedApplicationsForGroup
parameters:
- name: after
@@ -885,14 +885,14 @@ paths:
summary: Assign a role to a group
description: >-
Assigns a [standard
- role](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#standard-roles) to a group.
+ role](https://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#standard-roles) to a group.
You can also assign a custom role to a group, but the preferred method
to assign a custom role to a group is to create a binding between the
custom role, the resource set, and the group. See [Create a role
resource set
- binding](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/RoleDResourceSetBinding/#tag/RoleDResourceSetBinding/operation/createResourceSetBinding).
+ binding](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/RoleDResourceSetBinding/#tag/RoleDResourceSetBinding/operation/createResourceSetBinding).
> **Notes:**
@@ -1110,7 +1110,7 @@ paths:
> If you need a role assignment that applies to all apps, delete the
`APP_ADMIN` role assignment with the target and create another one. See
[Unassign a group
- role](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/RoleAssignmentBGroup/#tag/RoleAssignmentBGroup/operation/unassignRoleFromGroup).
+ role](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/RoleAssignmentBGroup/#tag/RoleAssignmentBGroup/operation/unassignRoleFromGroup).
operationId: unassignAppTargetToAdminRoleForGroup
responses:
'204':
@@ -1187,7 +1187,7 @@ paths:
> If you need a role assignment that applies to all apps, delete the
`APP_ADMIN` role assignment with the target and create another one. See
[Unassign a group
- role](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/RoleAssignmentBGroup/#tag/RoleAssignmentBGroup/operation/unassignRoleFromGroup).
+ role](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/RoleAssignmentBGroup/#tag/RoleAssignmentBGroup/operation/unassignRoleFromGroup).
operationId: unassignAppInstanceTargetToAppAdminRoleForGroup
responses:
'204':
@@ -1218,7 +1218,7 @@ paths:
summary: List all group role group targets
description: >-
Lists all group targets for a
- [`USER_ADMIN`](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#standard-roles),
+ [`USER_ADMIN`](https://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#standard-roles),
`HELP_DESK_ADMIN`, or `GROUP_MEMBERSHIP_ADMIN` role assignment to a
group.
@@ -1260,7 +1260,7 @@ paths:
summary: Assign a group role group target
description: >-
Assigns a group target to a
- [`USER_ADMIN`](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#standard-roles),
+ [`USER_ADMIN`](https://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#standard-roles),
`HELP_DESK_ADMIN`, or `GROUP_MEMBERSHIP_ADMIN` role assignment to a
group.
@@ -1291,7 +1291,7 @@ paths:
summary: Unassign a group role group target
description: >-
Unassigns a group target from a
- [`USER_ADMIN`](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#standard-roles),
+ [`USER_ADMIN`](https://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#standard-roles),
`HELP_DESK_ADMIN`, or `GROUP_MEMBERSHIP_ADMIN` role assignment to a
group.
operationId: unassignGroupTargetFromGroupAdminRole
@@ -1477,7 +1477,7 @@ components:
_links:
description: >-
[Discoverable
- resources](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/listGroups!c=200&path=_links&t=response)
+ resources](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/listGroups!c=200&path=_links&t=response)
related to the group
allOf:
- $ref: '#/components/schemas/LinksSelf'
@@ -1578,7 +1578,7 @@ components:
Enabled app features
> **Note:** See [Application
- Features](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationFeatures/)
+ Features](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationFeatures/)
for app provisioning features.
readOnly: true
items:
@@ -1774,14 +1774,14 @@ components:
Language](https://datatracker.ietf.org/doc/html/draft-kelly-json-hal-06)
specification. If the `expand=user/{userId}` query parameter is
specified, then the assigned [Application
- User](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/) is
+ User](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/) is
embedded.
properties:
user:
type: object
description: >-
The specified [Application
- User](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/)
+ User](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/)
assigned to the app
additionalProperties:
type: object
@@ -1946,7 +1946,7 @@ components:
type: string
description: >-
Specify the standard or IAM-based role type. See [standard
- roles](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#standard-roles).
+ roles](https://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#standard-roles).
CustomRoleAssignmentSchema:
title: Custom Role
type: object
@@ -1984,7 +1984,7 @@ components:
readOnly: true
description: >-
Features supported by the app. See app
- [features](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/listApplications!c=200&path=0/features&t=response).
+ [features](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/listApplications!c=200&path=0/features&t=response).
items:
type: string
id:
@@ -2008,7 +2008,7 @@ components:
type: array
description: >-
Authentication mode for the app. See app
- [signOnMode](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/listApplications!c=200&path=0/signOnMode&t=response).
+ [signOnMode](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/listApplications!c=200&path=0/signOnMode&t=response).
items:
type: string
status:
@@ -2080,7 +2080,7 @@ components:
type: string
description: >-
The ID of the realm in which the user is residing. See
- [Realms](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Realm/).
+ [Realms](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Realm/).
example: guo1bfiNtSnZYILxO0g4
readOnly: true
status:
@@ -2107,7 +2107,7 @@ components:
description: >-
The user type that determines the schema for the user's profile. The
`type` property is a map that identifies the [User
- Types](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserType/#tag/UserType).
+ Types](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserType/#tag/UserType).
Currently it contains a single element, `id`. It can be specified
@@ -2145,9 +2145,9 @@ components:
For a collection of users, the links object contains only the `self`
link. Operations that return a collection of users include [List all
- users](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#tag/User/operation/listUsers)
+ users](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#tag/User/operation/listUsers)
and [List all group member
- users](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/listGroupUsers).
+ users](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/listGroupUsers).
allOf:
- $ref: '#/components/schemas/LinksSelf'
- type: object
@@ -2223,7 +2223,7 @@ components:
You can extend group profiles with custom properties, but you must first
add the properties to the group profile schema before you can reference
them. Use the Profile Editor in the Admin Console or the [Schemas
- API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Schema/)to
+ API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Schema/)to
manage schema extensions.
@@ -2681,7 +2681,7 @@ components:
[pattern](https://developer.okta.com/docs/reference/api/schemas/#login-pattern-validation)
for `login`. You can use the Profile Editor in the Admin Console or the
[Schemas
- API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UISchema/#tag/UISchema)
+ API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UISchema/#tag/UISchema)
to make schema modifications.
@@ -2689,7 +2689,7 @@ components:
the custom property to the user profile schema before you reference it.
You can use the Profile Editor in the Admin Console or the [Schemas
- API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UISchema/#tag/UISchema)
+ API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UISchema/#tag/UISchema)
to manage schema extensions.
@@ -2796,7 +2796,7 @@ components:
that include @-signs. (By default, usernames must be formatted as
email addresses and thus always include @-signs. You can remove that
restriction using either the Admin Console or the [Schemas
- API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Schema/).
+ API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Schema/).
Users can sign in with their non-qualified short name (for example:
isaac.brock with username isaac.brock@example.com) as long as the
short name is still unique within the organization.
@@ -3022,7 +3022,7 @@ components:
- $ref: '#/components/schemas/HrefObject'
- description: >-
Link to the [Application
- Groups](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationGroups/#tag/ApplicationGroups/operation/listApplicationGroupAssignments)
+ Groups](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationGroups/#tag/ApplicationGroups/operation/listApplicationGroupAssignments)
resource
HelpLink:
allOf:
@@ -3033,14 +3033,14 @@ components:
- $ref: '#/components/schemas/HrefObject'
- description: >-
Link to the [SAML
- metadata](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationSSO/#tag/ApplicationSSO/operation/previewSAMLmetadataForApplication)
+ metadata](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationSSO/#tag/ApplicationSSO/operation/previewSAMLmetadataForApplication)
for SSO
UsersLink:
allOf:
- $ref: '#/components/schemas/HrefObject'
- description: >-
Link to the [Application
- Users](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/#tag/ApplicationUsers/operation/listApplicationUsers)
+ Users](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/#tag/ApplicationUsers/operation/listApplicationUsers)
resource
HrefObjectAssigneeLink:
allOf:
@@ -3167,7 +3167,7 @@ components:
from some other store. Okta supports the BCRYPT, SHA-512, SHA-256,
SHA-1, MD5, and PBKDF2 hash functions for password import.
A hashed password may be specified in a password object when creating or updating a user, but not for other operations.
- See the [Create user with imported hashed password](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-with-imported-hashed-password) description. When you update a user with a hashed password, the user must be in the `STAGED` status.
+ See the [Create user with imported hashed password](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-with-imported-hashed-password) description. When you update a user with a hashed password, the user must be in the `STAGED` status.
type: object
properties:
algorithm:
@@ -3225,7 +3225,7 @@ components:
PasswordCredentialHook:
description: >-
Specify a [password import inline
- hook](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/InlineHook/#tag/InlineHook/operation/createPasswordImportInlineHook)
+ hook](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/InlineHook/#tag/InlineHook/operation/createPasswordImportInlineHook)
to trigger verification of the user's password the first time the user
signs in. This allows an existing password to be imported into Okta
directly from some other store.
diff --git a/providers/src/okta/v00.00.00000/services/iam.yaml b/providers/src/okta/v00.00.00000/services/iam.yaml
index 51f2b4d5..a6d3fe2c 100644
--- a/providers/src/okta/v00.00.00000/services/iam.yaml
+++ b/providers/src/okta/v00.00.00000/services/iam.yaml
@@ -400,13 +400,13 @@ paths:
summary: Create a resource set
description: >-
Creates a new resource set. See [Supported
- resources](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#supported-resources).
+ resources](https://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#supported-resources).
> **Note:** The maximum number of `resources` allowed in a resource set
object is 1000. Resources are identified by either an Okta Resource Name
(ORN) or by a REST URL format. See [Okta Resource
- Name](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#okta-resource-name-orn).
+ Name](https://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#okta-resource-name-orn).
operationId: createResourceSet
x-codegen-request-body-name: instance
requestBody:
@@ -1657,7 +1657,7 @@ components:
The endpoint (URL) that references all resource objects included in
the resource set. Resources are identified by either an Okta
Resource Name (ORN) or by a REST URL format. See [Okta Resource
- Name](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#okta-resource-name-orn).
+ Name](https://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#okta-resource-name-orn).
maximum: 1000
items:
type: string
@@ -1920,7 +1920,7 @@ components:
type: array
description: >-
Array of permissions that the role grants. See
- [Permissions](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/guides/permissions).
+ [Permissions](https://developer.okta.com/docs/api/openapi/okta-management/guides/permissions).
required:
- label
- description
@@ -1978,7 +1978,7 @@ components:
type: array
description: >-
Array of permissions assigned to the role. See
- [Permissions](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/guides/permissions).
+ [Permissions](https://developer.okta.com/docs/api/openapi/okta-management/guides/permissions).
items:
$ref: '#/components/schemas/Permission'
Permission:
@@ -1995,7 +1995,7 @@ components:
type: string
description: >-
The assigned Okta
- [permission](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/guides/permissions)
+ [permission](https://developer.okta.com/docs/api/openapi/okta-management/guides/permissions)
readOnly: true
example: okta.users.read
lastUpdated:
@@ -2383,7 +2383,7 @@ components:
type: string
example: okta.users.manage
required: true
- description: An Okta [permission](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/guides/permissions)
+ description: An Okta [permission](https://developer.okta.com/docs/api/openapi/okta-management/guides/permissions)
examples:
RoleAssignedUsersResponseExample:
value:
diff --git a/providers/src/okta/v00.00.00000/services/identity_sources.yaml b/providers/src/okta/v00.00.00000/services/identity_sources.yaml
index 5172d621..cdd4f5f4 100644
--- a/providers/src/okta/v00.00.00000/services/identity_sources.yaml
+++ b/providers/src/okta/v00.00.00000/services/identity_sources.yaml
@@ -384,7 +384,7 @@ components:
Contains a set of external user attributes and their values that are
mapped to Okta standard and custom profile properties. See the
[`profile`
- object](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#tag/User/operation/getUser!c=200&path=profile&t=response)
+ object](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#tag/User/operation/getUser!c=200&path=profile&t=response)
and Declaration of a Custom Identity Source Schema in [Using anything as
a
source](https://help.okta.com/okta_help.htm?type=oie&id=ext-anything-as-a-source).
diff --git a/providers/src/okta/v00.00.00000/services/idps.yaml b/providers/src/okta/v00.00.00000/services/idps.yaml
index a684681f..3b21573b 100644
--- a/providers/src/okta/v00.00.00000/services/idps.yaml
+++ b/providers/src/okta/v00.00.00000/services/idps.yaml
@@ -106,7 +106,7 @@ paths:
You need to upload the whole trust chain as a single key using the [Key
Store
- API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProviderKeys/#tag/IdentityProviderKeys/operation/createIdentityProviderKey).
+ API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProviderKeys/#tag/IdentityProviderKeys/operation/createIdentityProviderKey).
Depending on the information stored in the smart card, select the proper
[template](https://developer.okta.com/docs/reference/okta-expression-language/#idp-user-profile)
@@ -533,7 +533,7 @@ paths:
> **Note:** The private key isn't listed in the [signing key credentials
for the identity provider
- (IdP)](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProviderSigningKeys/#tag/IdentityProviderSigningKeys/operation/listIdentityProviderSigningKeys)
+ (IdP)](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProviderSigningKeys/#tag/IdentityProviderSigningKeys/operation/listIdentityProviderSigningKeys)
until it's published.
operationId: generateCsrForIdentityProvider
x-codegen-request-body-name: metadata
@@ -799,9 +799,9 @@ paths:
> **Note:** To update an IdP with the newly generated key credential,
[update your
- IdP](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/replaceIdentityProvider)
+ IdP](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/replaceIdentityProvider)
using the returned key's `kid` in the [signing
- credential](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/replaceIdentityProvider!path=protocol/0/credentials/signing/kid&t=request).
+ credential](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/replaceIdentityProvider!path=protocol/0/credentials/signing/kid&t=request).
operationId: generateIdentityProviderSigningKey
parameters:
- name: validityYears
@@ -1071,7 +1071,7 @@ paths:
API.
The [Name Identifier
- Format](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/replaceIdentityProvider!path=protocol/0/settings&t=request)
+ Format](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/replaceIdentityProvider!path=protocol/0/settings&t=request)
of the incoming assertion must be
`urn:oasis:names:tc:SAML:2.0:nameid-format:persistent`.
operationId: linkUserToIdentityProvider
@@ -1196,7 +1196,7 @@ components:
`type`.
For policy actions supported by each IdP type, see [IdP type policy
- actions](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=policy&t=request).
+ actions](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=policy&t=request).
| Type |
@@ -1874,7 +1874,7 @@ components:
delegated access from the user
> **Note:** The [IdP
- type](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=type&t=request)
+ type](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=type&t=request)
table lists the scopes that are supported for each IdP.
items:
type: string
@@ -2204,7 +2204,7 @@ components:
The IdP Authorization Server (AS) endpoints are currently defined as
part of the [IdP
- provider]((https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=type&t=request))
+ provider]((https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=type&t=request))
and are read-only.
type: object
properties:
@@ -2224,7 +2224,7 @@ components:
user.
> **Note:** The [identity provider
- type](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=type&t=request)
+ type](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=type&t=request)
table lists the scopes that are supported for each IdP.
items:
type: string
@@ -2335,12 +2335,12 @@ components:
The IdP user is automatically linked to an Okta user when the
transformed IdP user matches an existing Okta user according to
[subject match
- rules](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=policy/subject&t=request).
+ rules](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=policy/subject&t=request).
DISABLED: >-
Okta never attempts to link the IdP user to an existing Okta user, but
may still attempt to provision a new Okta user according to the
[provisioning action
- type](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=policy/provisioning/action&t=request).
+ type](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=policy/provisioning/action&t=request).
PolicyAccountLinkFilter:
description: >-
Specifies filters on which users are available for account linking by an
@@ -2534,7 +2534,7 @@ components:
The `destination` property is required if request signatures are
specified. See [SAML 2.0 Request Algorithm
- object](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=protocol/0/algorithms/request&t=request).
+ object](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=protocol/0/algorithms/request&t=request).
maxLength: 512
example: https://idp.example.com/saml2/sso
url:
diff --git a/providers/src/okta/v00.00.00000/services/inlinehooks.yaml b/providers/src/okta/v00.00.00000/services/inlinehooks.yaml
index 1b83a675..5e33dd5a 100644
--- a/providers/src/okta/v00.00.00000/services/inlinehooks.yaml
+++ b/providers/src/okta/v00.00.00000/services/inlinehooks.yaml
@@ -15,12 +15,12 @@ paths:
following types are currently supported:
| Type Value | Name |
|------------------------------------|----------------------------------------------------------------|
- | `com.okta.import.transform` | [User import inline hook](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/InlineHook/#tag/InlineHook/operation/createUserImportInlineHook) |
- | `com.okta.oauth2.tokens.transform` | [Token inline hook](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/InlineHook/#tag/InlineHook/operation/createTokenInlineHook) |
- | `com.okta.saml.tokens.transform` | [SAML assertion inline hook](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/InlineHook/#tag/InlineHook/operation/createSAMLAssertionInlineHook) |
- | `com.okta.telephony.provider` | [Telephony inline hook](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/InlineHook/#tag/InlineHook/operation/createTelephonyInlineHook) |
- | `com.okta.user.credential.password.import` | [Password import inline hook](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/InlineHook/#tag/InlineHook/operation/createPasswordImportInlineHook)|
- | `com.okta.user.pre-registration` | [Registration inline hook](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/InlineHook/#tag/InlineHook/operation/create-registration-hook) |
+ | `com.okta.import.transform` | [User import inline hook](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/InlineHook/#tag/InlineHook/operation/createUserImportInlineHook) |
+ | `com.okta.oauth2.tokens.transform` | [Token inline hook](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/InlineHook/#tag/InlineHook/operation/createTokenInlineHook) |
+ | `com.okta.saml.tokens.transform` | [SAML assertion inline hook](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/InlineHook/#tag/InlineHook/operation/createSAMLAssertionInlineHook) |
+ | `com.okta.telephony.provider` | [Telephony inline hook](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/InlineHook/#tag/InlineHook/operation/createTelephonyInlineHook) |
+ | `com.okta.user.credential.password.import` | [Password import inline hook](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/InlineHook/#tag/InlineHook/operation/createPasswordImportInlineHook)|
+ | `com.okta.user.pre-registration` | [Registration inline hook](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/InlineHook/#tag/InlineHook/operation/create-registration-hook) |
operationId: listInlineHooks
parameters:
- $ref: '#/components/parameters/inlineHookType'
diff --git a/providers/src/okta/v00.00.00000/services/logs.yaml b/providers/src/okta/v00.00.00000/services/logs.yaml
index 07622621..f7953254 100644
--- a/providers/src/okta/v00.00.00000/services/logs.yaml
+++ b/providers/src/okta/v00.00.00000/services/logs.yaml
@@ -320,7 +320,7 @@ components:
zone:
description: >-
The `name` of the
- [Zone](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/NetworkZone/#tag/NetworkZone/operation/getNetworkZone)
+ [Zone](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/NetworkZone/#tag/NetworkZone/operation/getNetworkZone)
that the client's location is mapped to
type: string
readOnly: true
diff --git a/providers/src/okta/v00.00.00000/services/logstreams.yaml b/providers/src/okta/v00.00.00000/services/logstreams.yaml
index 4e004f42..72b6a16b 100644
--- a/providers/src/okta/v00.00.00000/services/logstreams.yaml
+++ b/providers/src/okta/v00.00.00000/services/logstreams.yaml
@@ -141,7 +141,7 @@ paths:
properties can't be modified after the log stream is initially created.
Use the [Retrieve the log stream schema for the schema
- type](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Schema/#tag/Schema/operation/getLogStreamSchema)
+ type](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Schema/#tag/Schema/operation/getLogStreamSchema)
request to determine which properties you can update for the specific
log stream type.
diff --git a/providers/src/okta/v00.00.00000/services/meta.yaml b/providers/src/okta/v00.00.00000/services/meta.yaml
index 6c60d02a..635bac88 100644
--- a/providers/src/okta/v00.00.00000/services/meta.yaml
+++ b/providers/src/okta/v00.00.00000/services/meta.yaml
@@ -21,7 +21,7 @@ paths:
The [User
- Types](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserType/)
+ Types](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserType/)
feature does not extend to apps. All users assigned to a given app use
the same app user schema. Therefore, unlike the user schema operations,
the app user schema operations all specify `default` and don't accept a
@@ -72,7 +72,7 @@ paths:
The [User
- Types](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserType/)
+ Types](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserType/)
feature does not extend to apps. All users assigned to a given app use
the same app user schema. Therefore, unlike the user schema operations,
the app user schema operations all specify `default` and don't accept a
@@ -131,7 +131,7 @@ paths:
The [User
- Types](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserType/)
+ Types](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserType/)
feature does not extend to groups. All groups use the same group schema.
Unlike user schema operations, group schema operations all specify
`default` and don't accept a schema ID.
@@ -179,7 +179,7 @@ paths:
The [User
- Types](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserType/)
+ Types](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserType/)
feature does not extend to groups. All groups use the same group schema.
Unlike user schema operations, group schema operations all specify
`default` and don't accept a schema ID.
@@ -503,7 +503,7 @@ paths:
You can't remove a property from the default schema if it's being
referenced as a
- [`matchAttribute`](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=policy/subject/matchAttribute&t=request)
+ [`matchAttribute`](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=policy/subject/matchAttribute&t=request)
in `SAML2` IdPs.
Currently, all validation of SAML assertions are only performed against
@@ -1775,7 +1775,7 @@ components:
**Note:** The `userType` field is an arbitrary string value and
isn't related to the newer [User
- Types](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserType/)
+ Types](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserType/)
feature.
zipCode:
allOf:
diff --git a/providers/src/okta/v00.00.00000/services/oauth2.yaml b/providers/src/okta/v00.00.00000/services/oauth2.yaml
index f67e164c..9434038d 100644
--- a/providers/src/okta/v00.00.00000/services/oauth2.yaml
+++ b/providers/src/okta/v00.00.00000/services/oauth2.yaml
@@ -44,7 +44,7 @@ paths:
summary: Assign a client role
description: >-
Assigns a [standard
- role](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#standard-roles) to a client
+ role](https://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#standard-roles) to a client
app.
@@ -52,7 +52,7 @@ paths:
method to assign a custom role to a client is to create a binding
between the custom role, the resource set, and the client app. See
[Create a role resource set
- binding](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/RoleDResourceSetBinding/#tag/RoleDResourceSetBinding/operation/createResourceSetBinding).
+ binding](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/RoleDResourceSetBinding/#tag/RoleDResourceSetBinding/operation/createResourceSetBinding).
> **Notes:**
@@ -268,7 +268,7 @@ paths:
> If you need a role assignment that applies to all apps, delete the
role assignment with the target and create another one. See [Unassign a
client
- role](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/RoleAssignmentClient/#tag/RoleAssignmentClient/operation/deleteRoleFromClient).
+ role](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/RoleAssignmentClient/#tag/RoleAssignmentClient/operation/deleteRoleFromClient).
operationId: removeAppTargetRoleFromClient
responses:
'204':
@@ -344,7 +344,7 @@ paths:
> If you need a role assignment that applies to all the apps, delete the
role assignment with the instance target and create another one. See
[Unassign a client
- role](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/RoleAssignmentClient/#tag/RoleAssignmentClient/operation/deleteRoleFromClient).
+ role](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/RoleAssignmentClient/#tag/RoleAssignmentClient/operation/deleteRoleFromClient).
operationId: removeAppTargetInstanceRoleForClient
responses:
'204':
@@ -375,7 +375,7 @@ paths:
summary: List all client role group targets
description: >-
Lists all group targets for a
- [`USER_ADMIN`](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#standard-roles),
+ [`USER_ADMIN`](https://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#standard-roles),
`HELP_DESK_ADMIN`, or `GROUP_MEMBERSHIP_ADMIN` role assignment to a
client. If the role isn't scoped to specific group targets, Okta returns
an empty array `[]`.
@@ -415,7 +415,7 @@ paths:
summary: Assign a client role group target
description: >-
Assigns a group target to a
- [`USER_ADMIN`](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#standard-roles),
+ [`USER_ADMIN`](https://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#standard-roles),
`HELP_DESK_ADMIN`, or `GROUP_MEMBERSHIP_ADMIN` role assignment to a
client app. When you assign the first group target, you reduce the scope
of the role assignment. The role no longer applies to all targets, but
@@ -451,7 +451,7 @@ paths:
assignment. If you need a role assignment that applies to all groups,
delete the role assignment with the target and create another one. See
[Unassign a client
- role](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/RoleAssignmentClient/#tag/RoleAssignmentClient/operation/deleteRoleFromClient).
+ role](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/RoleAssignmentClient/#tag/RoleAssignmentClient/operation/deleteRoleFromClient).
operationId: removeGroupTargetRoleFromClient
responses:
'204':
@@ -582,7 +582,7 @@ components:
type: string
description: >-
Specify the standard or IAM-based role type. See [standard
- roles](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#standard-roles).
+ roles](https://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#standard-roles).
CustomRoleAssignmentSchema:
title: Custom Role
type: object
@@ -620,7 +620,7 @@ components:
readOnly: true
description: >-
Features supported by the app. See app
- [features](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/listApplications!c=200&path=0/features&t=response).
+ [features](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/listApplications!c=200&path=0/features&t=response).
items:
type: string
id:
@@ -644,7 +644,7 @@ components:
type: array
description: >-
Authentication mode for the app. See app
- [signOnMode](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/listApplications!c=200&path=0/signOnMode&t=response).
+ [signOnMode](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/listApplications!c=200&path=0/signOnMode&t=response).
items:
type: string
status:
@@ -716,7 +716,7 @@ components:
_links:
description: >-
[Discoverable
- resources](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/listGroups!c=200&path=_links&t=response)
+ resources](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/listGroups!c=200&path=_links&t=response)
related to the group
allOf:
- $ref: '#/components/schemas/LinksSelf'
@@ -863,7 +863,7 @@ components:
You can extend group profiles with custom properties, but you must first
add the properties to the group profile schema before you can reference
them. Use the Profile Editor in the Admin Console or the [Schemas
- API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Schema/)to
+ API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Schema/)to
manage schema extensions.
diff --git a/providers/src/okta/v00.00.00000/services/orgs.yaml b/providers/src/okta/v00.00.00000/services/orgs.yaml
index aafd8a04..c8e24e52 100644
--- a/providers/src/okta/v00.00.00000/services/orgs.yaml
+++ b/providers/src/okta/v00.00.00000/services/orgs.yaml
@@ -213,7 +213,7 @@ components:
`lastName`, and `login`.
See
- [profile](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#tag/User/operation/getUser!c=200&path=profile&t=response)
+ [profile](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#tag/User/operation/getUser!c=200&path=profile&t=response)
for additional profile attributes.
properties:
firstName:
diff --git a/providers/src/okta/v00.00.00000/services/policies.yaml b/providers/src/okta/v00.00.00000/services/policies.yaml
index b20c1d16..bc3f92bd 100644
--- a/providers/src/okta/v00.00.00000/services/policies.yaml
+++ b/providers/src/okta/v00.00.00000/services/policies.yaml
@@ -379,7 +379,7 @@ paths:
> **Note:** Use [List all resources mapped to a
- Policy](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Policy/#tag/Policy/operation/listPolicyMappings)
+ Policy](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Policy/#tag/Policy/operation/listPolicyMappings)
to list all applications mapped to a policy.
operationId: listPolicyApps
responses:
@@ -1268,7 +1268,7 @@ components:
Enabled app features
> **Note:** See [Application
- Features](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationFeatures/)
+ Features](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationFeatures/)
for app provisioning features.
readOnly: true
items:
@@ -1464,14 +1464,14 @@ components:
Language](https://datatracker.ietf.org/doc/html/draft-kelly-json-hal-06)
specification. If the `expand=user/{userId}` query parameter is
specified, then the assigned [Application
- User](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/) is
+ User](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/) is
embedded.
properties:
user:
type: object
description: >-
The specified [Application
- User](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/)
+ User](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/)
assigned to the app
additionalProperties:
type: object
@@ -2071,7 +2071,7 @@ components:
- $ref: '#/components/schemas/HrefObject'
- description: >-
Link to the [Application
- Groups](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationGroups/#tag/ApplicationGroups/operation/listApplicationGroupAssignments)
+ Groups](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationGroups/#tag/ApplicationGroups/operation/listApplicationGroupAssignments)
resource
HelpLink:
allOf:
@@ -2082,14 +2082,14 @@ components:
- $ref: '#/components/schemas/HrefObject'
- description: >-
Link to the [SAML
- metadata](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationSSO/#tag/ApplicationSSO/operation/previewSAMLmetadataForApplication)
+ metadata](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationSSO/#tag/ApplicationSSO/operation/previewSAMLmetadataForApplication)
for SSO
UsersLink:
allOf:
- $ref: '#/components/schemas/HrefObject'
- description: >-
Link to the [Application
- Users](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/#tag/ApplicationUsers/operation/listApplicationUsers)
+ Users](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/ApplicationUsers/#tag/ApplicationUsers/operation/listApplicationUsers)
resource
HrefHints:
description: Describes allowed HTTP verbs for the `href`
diff --git a/providers/src/okta/v00.00.00000/services/privileged_access.yaml b/providers/src/okta/v00.00.00000/services/privileged_access.yaml
index cf9d44dd..83c14cd3 100644
--- a/providers/src/okta/v00.00.00000/services/privileged_access.yaml
+++ b/providers/src/okta/v00.00.00000/services/privileged_access.yaml
@@ -189,7 +189,7 @@ components:
containerOrn:
description: >-
The
- [ORN](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#okta-resource-name-orn)
+ [ORN](https://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#okta-resource-name-orn)
of the relevant resource.
diff --git a/providers/src/okta/v00.00.00000/services/realms.yaml b/providers/src/okta/v00.00.00000/services/realms.yaml
index 231d889d..6d8edde4 100644
--- a/providers/src/okta/v00.00.00000/services/realms.yaml
+++ b/providers/src/okta/v00.00.00000/services/realms.yaml
@@ -245,7 +245,7 @@ components:
Indicates the default realm. Existing users will start out in the
default realm and can be moved to other realms individually or
through realm assignments. See [Realms Assignments
- API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/RealmAssignment/).
+ API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/RealmAssignment/).
readOnly: true
lastUpdated:
type: string
diff --git a/providers/src/okta/v00.00.00000/services/risk.yaml b/providers/src/okta/v00.00.00000/services/risk.yaml
index 80f12814..0d889ec5 100644
--- a/providers/src/okta/v00.00.00000/services/risk.yaml
+++ b/providers/src/okta/v00.00.00000/services/risk.yaml
@@ -14,7 +14,7 @@ paths:
This request is used by a third-party risk provider to send IP risk
events to Okta. The third-party risk provider needs to be registered
with Okta before they can send events to Okta. See [Risk
- Providers](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/RiskProvider/).
+ Providers](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/RiskProvider/).
This API has a rate limit of 30 requests per minute. You can include
multiple risk events (up to a maximum of 20 events) in a single payload
diff --git a/providers/src/okta/v00.00.00000/services/roles.yaml b/providers/src/okta/v00.00.00000/services/roles.yaml
index 363bb313..a445bc07 100644
--- a/providers/src/okta/v00.00.00000/services/roles.yaml
+++ b/providers/src/okta/v00.00.00000/services/roles.yaml
@@ -323,7 +323,7 @@ components:
description: >-
A reference to an existing role. Standard roles require a `roleType`,
while Custom Roles require a `roleId`. See [Standard
- Roles](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#standard-roles).
+ Roles](https://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#standard-roles).
required: true
schema:
oneOf:
diff --git a/providers/src/okta/v00.00.00000/services/security.yaml b/providers/src/okta/v00.00.00000/services/security.yaml
index c9fd46e8..46376196 100644
--- a/providers/src/okta/v00.00.00000/services/security.yaml
+++ b/providers/src/okta/v00.00.00000/services/security.yaml
@@ -22,9 +22,9 @@ paths:
For SET JWT header and body descriptions, see [SET JWT
- header](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/SSFSecurityEventToken/#tag/SSFSecurityEventToken/schema/SecurityEventTokenRequestJwtHeader)
+ header](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/SSFSecurityEventToken/#tag/SSFSecurityEventToken/schema/SecurityEventTokenRequestJwtHeader)
and [SET JWT body
- payload](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/SSFSecurityEventToken/#tag/SSFSecurityEventToken/schema/SecurityEventTokenRequestJwtBody).
+ payload](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/SSFSecurityEventToken/#tag/SSFSecurityEventToken/schema/SecurityEventTokenRequestJwtBody).
content:
application/secevent+jwt:
schema:
diff --git a/providers/src/okta/v00.00.00000/services/templates.yaml b/providers/src/okta/v00.00.00000/services/templates.yaml
index cf22c3f1..4e188007 100644
--- a/providers/src/okta/v00.00.00000/services/templates.yaml
+++ b/providers/src/okta/v00.00.00000/services/templates.yaml
@@ -256,7 +256,7 @@ components:
type: string
description: >-
Text of the Template, including any
- [macros](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Template/)
+ [macros](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Template/)
maxLength: 161
minLength: 1
translations:
diff --git a/providers/src/okta/v00.00.00000/services/threats.yaml b/providers/src/okta/v00.00.00000/services/threats.yaml
index d107e4ec..bde27d49 100644
--- a/providers/src/okta/v00.00.00000/services/threats.yaml
+++ b/providers/src/okta/v00.00.00000/services/threats.yaml
@@ -102,7 +102,7 @@ components:
type: array
description: >-
Accepts a list of [Network
- Zone](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/NetworkZone/) IDs.
+ Zone](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/NetworkZone/) IDs.
IPs in the excluded network zones aren't logged or blocked.
diff --git a/providers/src/okta/v00.00.00000/services/users.yaml b/providers/src/okta/v00.00.00000/services/users.yaml
index ba041c4e..3750f1bd 100644
--- a/providers/src/okta/v00.00.00000/services/users.yaml
+++ b/providers/src/okta/v00.00.00000/services/users.yaml
@@ -63,11 +63,11 @@ paths:
This operation searches many properties:
* Any user profile attribute, including custom-defined attributes
* The top-level properties: `id`, `status`, `created`, `activated`, `statusChanged`, and `lastUpdated`
- * The [user type](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserType/#tag/UserType/operation/updateUserType) accessed as `type.id`
+ * The [user type](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserType/#tag/UserType/operation/updateUserType) accessed as `type.id`
> **Note:** The ability to
search by user classification is available as an [Early
- Access](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/guides/release-lifecycle/#early-access-ea)
+ Access](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/guides/release-lifecycle/#early-access-ea)
feature. The `classification.type` property cannot be used in
conjunction with other search terms. You can search using
`classification.type eq "LITE"` or `classification.type eq
@@ -341,7 +341,7 @@ paths:
For more information about the various scenarios of creating a user
listed in the examples, see the [User creation
- scenarios](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#user-creation-scenarios)
+ scenarios](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#user-creation-scenarios)
section.
operationId: createUser
parameters:
@@ -349,7 +349,7 @@ paths:
in: query
description: >-
Executes an [activation
- lifecycle](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserLifecycle/#tag/UserLifecycle/operation/activateUser)
+ lifecycle](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserLifecycle/#tag/UserLifecycle/operation/activateUser)
operation when creating the user
schema:
type: boolean
@@ -522,7 +522,7 @@ paths:
properly. Logins with a `/` character can only be fetched by `id` due to
URL issues with escaping the `/` character. If you don't know a user's
ID, you can use the [List all
- users](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#tag/User/operation/listUsers)
+ users](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#tag/User/operation/listUsers)
endpoint to find it.
@@ -613,11 +613,11 @@ paths:
If you are using this endpoint to set a password, it sets a password
without validating existing user credentials. This is an administrative
operation. For operations that validate credentials, refer to the [Reset
- password](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserCred/#tag/UserCred/operation/resetPassword),
+ password](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserCred/#tag/UserCred/operation/resetPassword),
[Start forgot password
- flow](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserCred/#tag/UserCred/operation/forgotPassword),
+ flow](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserCred/#tag/UserCred/operation/forgotPassword),
and [Update
- password](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserCred/#tag/UserCred/operation/changePassword)
+ password](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserCred/#tag/UserCred/operation/changePassword)
endpoints.
operationId: updateUser
parameters:
@@ -856,7 +856,7 @@ paths:
> **Note:** To list all apps in an org, use the [List all applications
endpoint in the Applications
- API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/listApplications).
+ API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/listApplications).
operationId: listAppLinks
responses:
'200':
@@ -935,7 +935,7 @@ paths:
> **Note:** To list all groups in your org, use the [List all groups
endpoints in the Groups
- API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/listGroups).
+ API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/listGroups).
operationId: listUserGroups
responses:
'200':
@@ -1037,7 +1037,7 @@ paths:
password.
> See [Create user with optional
- password](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-with-optional-password).
+ password](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-with-optional-password).
> **Legal disclaimer**
@@ -1280,17 +1280,17 @@ paths:
Perform this operation only on users with a `PROVISIONED` or `RECOVERY`
- [status](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#tag/User/operation/listUsers!c=200&path=status&t=response).
+ [status](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#tag/User/operation/listUsers!c=200&path=status&t=response).
This operation restarts the activation workflow if for some reason the
user activation wasn't completed when using the `activationToken` from
[Activate
- User](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserLifecycle/#tag/UserLifecycle/operation/activateUser).
+ User](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserLifecycle/#tag/UserLifecycle/operation/activateUser).
Users that don't have a password must complete the flow by completing
the [Reset
- password](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserCred/#tag/UserCred/operation/resetPassword)
+ password](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserCred/#tag/UserCred/operation/resetPassword)
flow and MFA enrollment steps to transition the user to `ACTIVE` status.
@@ -1890,7 +1890,7 @@ paths:
> **Note:** To list all client resources for which a specified
authorization server has tokens, use the [List all client resources for
an authorization server in the Authorization Servers
- API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/AuthorizationServerClients/#tag/AuthorizationServerClients/operation/listOAuth2ClientsForAuthorizationServer).
+ API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/AuthorizationServerClients/#tag/AuthorizationServerClients/operation/listOAuth2ClientsForAuthorizationServer).
operationId: listUserClients
responses:
'200':
@@ -2168,7 +2168,7 @@ paths:
You can only perform this operation on users in `STAGED`, `ACTIVE`,
`PASSWORD_EXPIRED`, or `RECOVERY` status that have a valid [password
- credential](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#tag/User/operation/createUser!path=credentials/password&t=request).
+ credential](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#tag/User/operation/createUser!path=credentials/password&t=request).
The user transitions to `ACTIVE` status when successfully invoked in
@@ -2237,7 +2237,7 @@ paths:
You can only perform this operation on users in `STAGED`, `ACTIVE`, or
`RECOVERY` status that have a valid [password
- credential](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#tag/User/operation/createUser!path=credentials/password&t=request).
+ credential](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#tag/User/operation/createUser!path=credentials/password&t=request).
operationId: changeRecoveryQuestion
x-codegen-request-body-name: userCredentials
requestBody:
@@ -2295,7 +2295,7 @@ paths:
status and
a valid [recovery question
- credential](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#tag/User/operation/createUser!path=credentials/recovery_question&t=request).
+ credential](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#tag/User/operation/createUser!path=credentials/recovery_question&t=request).
> **Note:** If you have migrated to Identity Engine, you can allow users
@@ -2413,7 +2413,7 @@ paths:
> **Note:** To list all devices registered to an org, use the [List all
devices endpoint in the Devices
- API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Device/#tag/Device/operation/listDevices).
+ API](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Device/#tag/Device/operation/listDevices).
operationId: listUserDevices
responses:
'200':
@@ -2453,7 +2453,7 @@ paths:
description: >-
Lists all enrolled factors for the specified user that are included in
the highest priority [authenticator enrollment
- policy](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Policy/)
+ policy](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Policy/)
that applies to the user.
@@ -2719,7 +2719,7 @@ paths:
description: >-
Lists all the supported factors that can be enrolled for the specified
user that are included in the highest priority [authenticator enrollment
- policy](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Policy/)
+ policy](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Policy/)
that applies to the user.
@@ -3045,8 +3045,8 @@ paths:
> **Note:**
> The response body for a number matching push challenge to an Okta Verify `push` factor enrollment is different from the response body of a standard push challenge.
- > The number matching push challenge [response body](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/getFactorTransactionStatus!c=200&path=1/_embedded&t=response) contains the correct answer for the challenge.
- > Use [Verify a factor](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/verifyFactor) to configure which challenge is sent.
+ > The number matching push challenge [response body](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/getFactorTransactionStatus!c=200&path=1/_embedded&t=response) contains the correct answer for the challenge.
+ > Use [Verify a factor](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/verifyFactor) to configure which challenge is sent.
operationId: getFactorTransactionStatus
responses:
'200':
@@ -3102,12 +3102,12 @@ paths:
> - You can send standard push challenges or number matching push
challenges to Okta Verify `push` factor enrollments. Use a [request
- body](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/verifyFactor!path=2/useNumberMatchingChallenge&t=request)
+ body](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/verifyFactor!path=2/useNumberMatchingChallenge&t=request)
for number matching push challenges.
> - To verify a `push` factor, use the **poll** link returned when you
issue the challenge. See [Retrieve a factor transaction
- status](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/getFactorTransactionStatus).
+ status](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/getFactorTransactionStatus).
operationId: verifyFactor
parameters:
- name: templateId
@@ -3166,14 +3166,14 @@ paths:
> Unlike standard push challenges that don't require a request body, a
number matching
- [`push`](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/verifyFactor!path=2/useNumberMatchingChallenge&t=request)
+ [`push`](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/verifyFactor!path=2/useNumberMatchingChallenge&t=request)
challenge requires a request body. `useNumberMatchingChallenge` must
be set to `true`.
> When a number matching challenge is issued for an Okta Verify `push`
factor enrollment, a `correctAnswer` challenge object is returned in
the
- [`_embedded`](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/verifyFactor!c=200&path=_embedded&t=response)
+ [`_embedded`](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/verifyFactor!c=200&path=_embedded&t=response)
object.
content:
application/json:
@@ -3552,13 +3552,13 @@ paths:
summary: Assign a user role
description: >-
Assigns a [standard
- role](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#standard-roles) to a user.
+ role](https://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#standard-roles) to a user.
You can also assign a custom role to a user, but the preferred method to
assign a custom role to a user is to create a binding between the custom
role, the resource set, and the user. See [Create a role resource set
- binding](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/RoleDResourceSetBinding/#tag/RoleDResourceSetBinding/operation/createResourceSetBinding).
+ binding](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/RoleDResourceSetBinding/#tag/RoleDResourceSetBinding/operation/createResourceSetBinding).
> **Notes:**
@@ -4183,7 +4183,7 @@ paths:
You can also clear the user's remembered factors for all devices using
the `forgetDevices` parameter. See
- [forgetDevices](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserSessions/#tag/UserSessions/operation/revokeUserSessions!in=query&path=forgetDevices&t=request).
+ [forgetDevices](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserSessions/#tag/UserSessions/operation/revokeUserSessions!in=query&path=forgetDevices&t=request).
> **Note:** This operation doesn't clear the sessions created for web or
native apps.
@@ -4424,7 +4424,7 @@ components:
type: string
description: >-
The ID of the realm in which the user is residing. See
- [Realms](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Realm/).
+ [Realms](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Realm/).
example: guo1bfiNtSnZYILxO0g4
readOnly: true
status:
@@ -4451,7 +4451,7 @@ components:
description: >-
The user type that determines the schema for the user's profile. The
`type` property is a map that identifies the [User
- Types](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserType/#tag/UserType).
+ Types](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserType/#tag/UserType).
Currently it contains a single element, `id`. It can be specified
@@ -4489,9 +4489,9 @@ components:
For a collection of users, the links object contains only the `self`
link. Operations that return a collection of users include [List all
- users](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#tag/User/operation/listUsers)
+ users](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#tag/User/operation/listUsers)
and [List all group member
- users](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/listGroupUsers).
+ users](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/listGroupUsers).
allOf:
- $ref: '#/components/schemas/LinksSelf'
- type: object
@@ -4604,17 +4604,17 @@ components:
type: string
description: >-
The ID of the realm in which the user is residing. See
- [Realms](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Realm/).
+ [Realms](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Realm/).
example: guo1bfiNtSnZYILxO0g4
type:
type: object
description: >-
The ID of the user type. Add this value if you want to create a user
with a non-default [User
- Type](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserType/).
+ Type](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserType/).
The user type determines which
- [schema](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Schema/)
+ [schema](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Schema/)
applies to that user. After a user has been created, the user can
only be assigned a different user type by an administrator through a
@@ -4659,7 +4659,7 @@ components:
type: string
description: >-
The ID of the realm in which the user is residing. See
- [Realms](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Realm/).
+ [Realms](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Realm/).
example: guo1bfiNtSnZYILxO0g4
AssignedAppLink:
type: object
@@ -4761,7 +4761,7 @@ components:
_links:
description: >-
[Discoverable
- resources](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/listGroups!c=200&path=_links&t=response)
+ resources](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/listGroups!c=200&path=_links&t=response)
related to the group
allOf:
- $ref: '#/components/schemas/LinksSelf'
@@ -5769,7 +5769,7 @@ components:
type: string
description: >-
Specify the standard or IAM-based role type. See [standard
- roles](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#standard-roles).
+ roles](https://developer.okta.com/docs/api/openapi/okta-management/guides/roles/#standard-roles).
CustomRoleAssignmentSchema:
title: Custom Role
type: object
@@ -5856,7 +5856,7 @@ components:
readOnly: true
description: >-
Features supported by the app. See app
- [features](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/listApplications!c=200&path=0/features&t=response).
+ [features](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/listApplications!c=200&path=0/features&t=response).
items:
type: string
id:
@@ -5880,7 +5880,7 @@ components:
type: array
description: >-
Authentication mode for the app. See app
- [signOnMode](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/listApplications!c=200&path=0/signOnMode&t=response).
+ [signOnMode](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Application/#tag/Application/operation/listApplications!c=200&path=0/signOnMode&t=response).
items:
type: string
status:
@@ -5973,7 +5973,7 @@ components:
[pattern](https://developer.okta.com/docs/reference/api/schemas/#login-pattern-validation)
for `login`. You can use the Profile Editor in the Admin Console or the
[Schemas
- API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UISchema/#tag/UISchema)
+ API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UISchema/#tag/UISchema)
to make schema modifications.
@@ -5981,7 +5981,7 @@ components:
the custom property to the user profile schema before you reference it.
You can use the Profile Editor in the Admin Console or the [Schemas
- API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UISchema/#tag/UISchema)
+ API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UISchema/#tag/UISchema)
to manage schema extensions.
@@ -6088,7 +6088,7 @@ components:
that include @-signs. (By default, usernames must be formatted as
email addresses and thus always include @-signs. You can remove that
restriction using either the Admin Console or the [Schemas
- API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Schema/).
+ API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Schema/).
Users can sign in with their non-qualified short name (for example:
isaac.brock with username isaac.brock@example.com) as long as the
short name is still unique within the organization.
@@ -6279,7 +6279,7 @@ components:
You can extend group profiles with custom properties, but you must first
add the properties to the group profile schema before you can reference
them. Use the Profile Editor in the Admin Console or the [Schemas
- API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Schema/)to
+ API](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Schema/)to
manage schema extensions.
@@ -6505,7 +6505,7 @@ components:
delegated access from the user
> **Note:** The [IdP
- type](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=type&t=request)
+ type](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=type&t=request)
table lists the scopes that are supported for each IdP.
items:
type: string
@@ -6567,7 +6567,7 @@ components:
`type`.
For policy actions supported by each IdP type, see [IdP type policy
- actions](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=policy&t=request).
+ actions](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=policy&t=request).
| Type |
@@ -7189,7 +7189,7 @@ components:
allOf:
- description: >-
Verifies the factor resource. See [Verify a
- factor](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/verifyFactor).
+ factor](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/verifyFactor).
- $ref: '#/components/schemas/HrefObject'
readOnly: true
UserFactorVerifyResult:
@@ -7473,7 +7473,7 @@ components:
credential. The user's current provider is managed by the **Delegated
Authentication** settings in your org. See [Create user with
authentication
- provider](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-with-authentication-provider).
+ provider](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-with-authentication-provider).
type: object
properties:
name:
@@ -7683,7 +7683,7 @@ components:
The IdP Authorization Server (AS) endpoints are currently defined as
part of the [IdP
- provider]((https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=type&t=request))
+ provider]((https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=type&t=request))
and are read-only.
type: object
properties:
@@ -7703,7 +7703,7 @@ components:
user.
> **Note:** The [identity provider
- type](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=type&t=request)
+ type](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=type&t=request)
table lists the scopes that are supported for each IdP.
items:
type: string
@@ -7794,7 +7794,7 @@ components:
- description: >-
Returns information about a specific authenticator. See
[Retrieve an
- authenticator](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Authenticator/#tag/Authenticator/operation/getAuthenticator).
+ authenticator](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Authenticator/#tag/Authenticator/operation/getAuthenticator).
- $ref: '#/components/schemas/HrefObject'
readOnly: true
AuthenticatorProfileTacRequest:
@@ -7865,7 +7865,7 @@ components:
from some other store. Okta supports the BCRYPT, SHA-512, SHA-256,
SHA-1, MD5, and PBKDF2 hash functions for password import.
A hashed password may be specified in a password object when creating or updating a user, but not for other operations.
- See the [Create user with imported hashed password](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-with-imported-hashed-password) description. When you update a user with a hashed password, the user must be in the `STAGED` status.
+ See the [Create user with imported hashed password](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-with-imported-hashed-password) description. When you update a user with a hashed password, the user must be in the `STAGED` status.
type: object
properties:
algorithm:
@@ -7923,7 +7923,7 @@ components:
PasswordCredentialHook:
description: >-
Specify a [password import inline
- hook](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/InlineHook/#tag/InlineHook/operation/createPasswordImportInlineHook)
+ hook](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/InlineHook/#tag/InlineHook/operation/createPasswordImportInlineHook)
to trigger verification of the user's password the first time the user
signs in. This allows an existing password to be imported into Okta
directly from some other store.
@@ -8077,7 +8077,7 @@ components:
allOf:
- description: >-
Activates an enrolled factor. See [Activate a
- factor](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/activateFactor).
+ factor](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/activateFactor).
- $ref: '#/components/schemas/HrefObject'
readOnly: true
LinksCancel:
@@ -8095,7 +8095,7 @@ components:
allOf:
- description: >-
Deactivates the factor. See [Unenroll a
- factor](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/unenrollFactor).
+ factor](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/unenrollFactor).
- $ref: '#/components/schemas/HrefObject'
readOnly: true
LinksEnroll:
@@ -8105,7 +8105,7 @@ components:
allOf:
- description: >-
Enrolls a supported factor. See [Enroll a
- factor](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/enrollFactor).
+ factor](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/enrollFactor).
- $ref: '#/components/schemas/HrefObject'
readOnly: true
LinksFactor:
@@ -8144,7 +8144,7 @@ components:
- description: >-
Lists all supported security questions. See [List all supported
security
- questions](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/listSupportedSecurityQuestions).
+ questions](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/listSupportedSecurityQuestions).
- $ref: '#/components/schemas/HrefObject'
readOnly: true
LinksResend:
@@ -8154,7 +8154,7 @@ components:
allOf:
- description: >-
Resends the factor enrollment challenge. See [Resend a factor
- enrollment](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/resendEnrollFactor).
+ enrollment](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/UserFactor/#tag/UserFactor/operation/resendEnrollFactor).
- $ref: '#/components/schemas/HrefObject'
readOnly: true
LinksSend:
@@ -8239,12 +8239,12 @@ components:
The IdP user is automatically linked to an Okta user when the
transformed IdP user matches an existing Okta user according to
[subject match
- rules](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=policy/subject&t=request).
+ rules](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=policy/subject&t=request).
DISABLED: >-
Okta never attempts to link the IdP user to an existing Okta user, but
may still attempt to provision a new Okta user according to the
[provisioning action
- type](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=policy/provisioning/action&t=request).
+ type](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=policy/provisioning/action&t=request).
PolicyAccountLinkFilter:
description: >-
Specifies filters on which users are available for account linking by an
@@ -8438,7 +8438,7 @@ components:
The `destination` property is required if request signatures are
specified. See [SAML 2.0 Request Algorithm
- object](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=protocol/0/algorithms/request&t=request).
+ object](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/IdentityProvider/#tag/IdentityProvider/operation/createIdentityProvider!path=protocol/0/algorithms/request&t=request).
maxLength: 512
example: https://idp.example.com/saml2/sso
url:
@@ -9351,7 +9351,7 @@ components:
create-user-without-credentials-request:
description: >-
See [Create user without
- credentials](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-without-credentials)
+ credentials](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-without-credentials)
value:
profile:
firstName: Isaac
@@ -9362,7 +9362,7 @@ components:
create-user-with-recovery-question-request:
description: >-
See [Create user with recovery
- question](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-with-recovery-question)
+ question](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-with-recovery-question)
value:
profile:
firstName: Isaac
@@ -9377,7 +9377,7 @@ components:
create-user-with-password-request:
description: >-
Set `activate` parameter to `true`. See [Create user with
- password](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-with-password).
+ password](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-with-password).
value:
profile:
firstName: Isaac
@@ -9392,7 +9392,7 @@ components:
description: >-
Set `activate` parameter to `true`. See [Create user with imported
hashed
- password](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-with-imported-hashed-password).
+ password](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-with-imported-hashed-password).
value:
profile:
firstName: Isaac
@@ -9411,7 +9411,7 @@ components:
description: >-
Set `activate` parameter to `true`. See [Create user with password
import inline
- hook](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-with-password-import-inline-hook).
+ hook](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-with-password-import-inline-hook).
value:
profile:
firstName: Isaac
@@ -9426,7 +9426,7 @@ components:
create-user-with-password-and-recovery-question-request:
description: >-
See [Create user with password and recovery
- question](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-with-password-and-recovery-question)
+ question](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-with-password-and-recovery-question)
value:
profile:
firstName: Isaac
@@ -9443,7 +9443,7 @@ components:
create-user-with-authentication-provider-request:
description: >-
Set `activate` parameter to `true`. See [Create user with authentication
- provider](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-with-authentication-provider).
+ provider](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-with-authentication-provider).
value:
profile:
firstName: Isaac
@@ -9458,7 +9458,7 @@ components:
create-user-in-group-request:
description: >-
See [Create user in
- group](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-in-group)
+ group](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-in-group)
value:
profile:
firstName: Isaac
@@ -9472,7 +9472,7 @@ components:
create-user-with-non-default-user-type-request:
description: >-
See [Create user with non-default user
- type](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-with-non-default-user-type)
+ type](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/User/#create-user-with-non-default-user-type)
value:
profile:
firstName: Isaac
diff --git a/providers/src/okta/v00.00.00000/services/zones.yaml b/providers/src/okta/v00.00.00000/services/zones.yaml
index 9b5463fc..b7859808 100644
--- a/providers/src/okta/v00.00.00000/services/zones.yaml
+++ b/providers/src/okta/v00.00.00000/services/zones.yaml
@@ -238,9 +238,9 @@ paths:
> **Notes:**
> * You can't delete a Network Zone that's used by a
- [Policy](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Policy/)
+ [Policy](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Policy/)
or
- [Rule](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Policy/#tag/Policy/operation/listPolicyRules).
+ [Rule](https://developer.okta.com/docs/apihttps://developer.okta.com/docs/api/openapi/okta-management/management/tag/Policy/#tag/Policy/operation/listPolicyRules).
> * For Okta Identity Engine orgs, you can't delete a Network Zone with
an ACTIVE `status`.