AWS SSO OIDC

Name: AWS SSO OIDC API
Brand: AWS SSO OIDC
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthAuthenticationapiKey3 EndpointsREST

For Agents

Run the OAuth 2.0 device authorisation flow with IAM Identity Center to obtain a bearer access token. Agents register a client, start device authorisation, and exchange the code for a token.

Install Jentic One Beta

Connect the AWS SSO OIDC to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS SSO OIDC, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with AWS SSO OIDC API.

Start a device authorisation flow with StartDeviceAuthorization and receive a verification URL plus device code

Exchange a verified device code for an access token via CreateToken

GET STARTED

Start building with AWS SSO OIDC API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for AWS SSO OIDC, keeping it validated and agent-ready. AWS IAM Identity Center OIDC implements the OAuth 2.0 Device Authorization Grant flow so that CLIs and native applications can sign users into IAM Identity Center without an embedded browser. The three operations let a tool register itself as an OIDC client, start a device authorisation, and exchange the resulting device code for an access token. The issued bearer token is then consumed by the IAM Identity Center Portal to list accounts and roles.

Use Cases

Patterns agents use AWS SSO OIDC API for, with concrete tasks.

★ CLI Sign-In via Device Authorisation

Command-line tools and developer utilities use the OIDC device flow to sign users into IAM Identity Center without launching a browser inside the terminal. RegisterClient registers the tool once, StartDeviceAuthorization returns a userCode and verificationUriComplete that the user opens in a browser, and CreateToken polls until approval, then returns the access token.

RegisterClient with clientName='my-cli' and clientType='public', call StartDeviceAuthorization to get verificationUriComplete and deviceCode, then poll CreateToken with grantType='urn:ietf:params:oauth:grant-type:device_code' until accessToken is returned.

Native Application Single Sign-On

Desktop tools that operate against many AWS accounts use the OIDC device flow as their authentication primitive: one sign-in produces an access token, the tool then uses ListAccounts and GetRoleCredentials to surface a role picker, and the resulting sigv4 credentials sign every other AWS call.

RegisterClient for the native app, run StartDeviceAuthorization, and once the user approves call CreateToken to obtain the bearer token to feed into the SSO Portal API.

Token Refresh Loop

IAM Identity Center access tokens expire after a configured lifetime. Tools call CreateToken with grantType='refresh_token' and the previously-issued refreshToken to obtain a new access token without re-prompting the user, until the refresh token itself expires.

Call CreateToken with grantType='refresh_token' and the cached refreshToken; if the response is a TokenError, fall back to a new device authorisation flow.

AI Agent Federated Sign-In via Jentic

AI agents using Jentic that operate on behalf of an IAM Identity Center user can run the device flow once at setup and let Jentic handle all subsequent token exchange. The user sees the device code, approves it in a browser, and the resulting bearer token lives in the Jentic vault — never in the agent's prompt.

Search Jentic for 'start aws sso device authorization', execute StartDeviceAuthorization with the registered clientId and clientSecret, surface the verificationUriComplete to the user, then poll CreateToken until the access token is returned.

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for aws sso oidc, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/client/register

POST

/device_authorization

Start a device authorisation flow (StartDeviceAuthorization)

POST

/token

Exchange a device code or refresh token for an access token (CreateToken)

POST

/client/register

POST

/device_authorization

Start a device authorisation flow (StartDeviceAuthorization)

POST

/token

Exchange a device code or refresh token for an access token (CreateToken)

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Registered clientId, clientSecret, and the issued access and refresh tokens are stored encrypted in the Jentic vault. Token polling and refresh happen server-side — the agent receives only what it needs to surface the verification URL to the user.

Intent-based discovery

Agents search by intent (for example, 'start aws sso device flow' or 'exchange device code for token') and Jentic returns the matching sso-oidc operations with input schemas, letting the agent invoke RegisterClient, StartDeviceAuthorization, and CreateToken in sequence.

Time to first call

Direct sso-oidc integration: 1 day for client registration, polling logic, refresh handling, and error retries (SlowDown, AuthorizationPendingException). Through Jentic: under 30 minutes — search, load schemas, execute the three-step flow.

FAQs

Specific to using AWS SSO OIDC API through Jentic.

Why is there no official OpenAPI spec for AWS SSO OIDC?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS SSO OIDC via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the AWS SSO OIDC use?

RegisterClient and StartDeviceAuthorization are unauthenticated calls (the regional endpoint is open). CreateToken authenticates the registered client via clientId and clientSecret returned at registration. The resulting bearer token is then used against the SSO Portal API. Through Jentic, the clientId, clientSecret, and resulting tokens are stored encrypted in the vault.

Can I use SSO OIDC for browser-based single sign-on?

AWS SSO OIDC currently implements only the OAuth 2.0 Device Authorization Grant flow (RFC 8628), which is designed for CLIs and native applications. Authorization Code with PKCE is not yet exposed through this API — for browser-based login, use the IAM Identity Center sign-in URLs directly.

What are the rate limits for the AWS SSO OIDC?

AWS does not publish fixed per-second limits for sso-oidc. CreateToken returns a SlowDown error when the client polls too frequently before user approval — the StartDeviceAuthorization response includes an interval (typically 5 seconds) that the client must respect.

How do I run the device authorisation flow through Jentic?

Through Jentic, RegisterClient once with clientType='public', then StartDeviceAuthorization to obtain verificationUriComplete and deviceCode, surface that URL to the user, and poll CreateToken (grantType='urn:ietf:params:oauth:grant-type:device_code') at the returned interval until accessToken is issued. Jentic stores the resulting tokens in the vault.

Is the AWS SSO OIDC free?

IAM Identity Center, including its OIDC endpoints, is offered at no additional charge. You pay only for the underlying AWS resources accessed through the federated roles.

AWS SSO OIDC

Connect the AWS SSO OIDC to your agent

Capabilities

Start building with AWS SSO OIDC API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs