Services

Resources

Company

/

Single sign-on (SSO)

Single sign-on (SSO)

Single sign-on (SSO) lets you log in once, at an identity provider (IdP), and then open many applications without another password prompt. Okta, Microsoft Entra ID, Google Workspace and AWS IAM Identity Center are common IdPs. Each application trusts a statement the IdP signs about who you are. SSO covers the first half of authentication vs authorization. What you may do inside each app is still decided by that app.

How it works

Two protocols carry the signed statement. SAML 2.0 posts an XML assertion through the browser to the app. OpenID Connect (OIDC) is built on OAuth 2.0 and returns an ID token, a signed JSON Web Token. Older enterprise apps tend to speak SAML. CLIs, mobile apps and Kubernetes API servers mostly use OIDC.

Several clocks run at once. The IdP session decides how often you see its login page. After login, each app keeps its own cookie or tokens. Disable a user at the IdP and new logins stop at once. Sessions the apps already handed out keep working until they expire, so short app tokens matter.

AWS IAM Identity Center brings this to the terminal. aws sso login opens a browser and caches a token under ~/.aws/sso/cache. A profile in ~/.aws/config names an account and a role, and the SDK trades the cached token for temporary role credentials. By default the Identity Center session lasts 8 hours and role credentials last 1 hour. So one morning login funds 8 hours / 1 hour = 8 silent refreshes.

One2N ran into the config side of this with cloudlens, its open-source CLI for AWS, written in Go. In the first week, a user reported that cloudlens could not read their SSO credentials. Their config used the newer layout, with sso_start_url in a separate [sso-session] block. Version 1 of the AWS SDK for Go only reads SSO keys from the profile section itself.

The team could ask every user to copy those keys back into each profile, or change the code. They upgraded to SDK v2 in cloudlens v0.1.2, which reads both layouts.

Why it matters in production

SSO puts every login behind one door. Turn on multi-factor authentication at the IdP and every app gets it. Offboarding becomes one switch, and an IdP outage locks people out of everything together. The bigger risk is quiet: one Identity Center group mapped to AdministratorAccess grants admin in every account it touches. Keep permission sets small with least privilege, and map IdP groups to app roles through role-based access control.

See also

On the One2N blog

References

  1. OpenID Connect Core 1.0

  2. AWS CLI User Guide: Configuring IAM Identity Center authentication

Hub and spoke diagram of single sign-on: you log in once at the IdP, which adds MFA and sends signed statements to an app that uses SAML and a CLI that uses OIDC. Red arrows from the IdP reach three AWS accounts, labelled 1 group: AdministratorAccess in every account. Below, Identity Center session 8 h ÷ role creds 1 h = 8 silent refreshes.