Repository navigation
data(readiness): list okta - #393
Merged
Merged
Conversation
Signed-off-by: Kam <oss@0state.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One listing for the job
user-create(Create a user), from agent readiness R2's cohort:POST /api/v1/users(createUser) on each organization's own Okta domain, declared from Okta's management OpenAPI document. API tokens are created only in the Admin Console; the API lists and revokes them but cannot create one, so no key operations are declared. Okta's MCP server runs locally, so no MCP interface is declared. Starter offers only a free trial, and every other plan says "Contact us". Buying goes through sales, so the contact-sales page is both the checkout and the access request in front of the API.Every field is bound to the vendor's own public page.