Sulat.com / Writing on AIThursday, November 19, 2026
Cloud Security/18 November 2026

Tobias Schmidt’s team moves its admin app’s login onto AWS IAM Identity Center

Tobias Schmidt's team is moving its internal admin app's login onto AWS IAM Identity Center, so the app shows up as one more tile in the sign-in portal. Setup is console-only, and removed users keep their session.

The IAM Identity Center logo as a 3D tile linked by a glowing line to a dashboard tile in a row of app tiles

At a glance

  • Tobias Schmidt of AWS Fundamentals says his team is moving its internal admin app's login onto AWS IAM Identity Center as a customer managed SAML 2.0 application.
  • Who gets in is now the user assignment on the app. Before, it was Basic Auth, and access meant changing a secret and redeploying.
  • AWS says SAML 2.0 customer managed applications can be created in the console only, with no API or CloudFormation support, so the team's dev and prod apps were set up by hand.
  • Removing someone in Identity Center stops new sign-ins, but the admin app's signed session cookie lives up to 7 days, which Schmidt accepts for a team of two.

Tobias Schmidt of AWS Fundamentals says his team is moving its internal admin app’s login onto AWS IAM Identity Center. In a thread on X on 17 November, he described the app as one more tile in the access portal the team already signs in to every day, set up as a customer managed SAML 2.0 application.

Identity Center is best known as the front door to AWS accounts. AWS documents the same service as a sign-in for your own apps too: any app that speaks SAML 2.0 can be added and assigned to users. Schmidt’s thread shows what that looks like for a team of two.

How the login works

Schmidt’s team created a customer managed SAML 2.0 application in Identity Center. When someone picks the tile, Identity Center sends a signed SAML response to the admin app’s API. The API checks the signature, the audience and the validity window before it lets the person in. Who gets in is the user assignment on the application, so the code holds no email allowlist.

Four-step flow: click portal tile, Identity Center signs SAML response, app checks it, session cookie issued
A click on the portal tile ends with the app checking the signed response and issuing its own session cookie.

Before the move, the app sat behind Basic Auth. Giving someone access meant changing a secret and redeploying. Now it means assigning that person to the application in Identity Center.

Before: change a secret then redeploy. Now: assign the person in Identity Center, no email list in code
Access used to mean a secret change and a redeploy; now it’s an assignment.

Setting up your own SAML app

AWS’s documentation covers the console steps for an app that isn’t in the catalog:

  1. Open the IAM Identity Center console, choose Applications, then the Customer managed tab, then Add application.
  2. Choose “I have an application I want to set up”, pick SAML 2.0 and name the application.
  3. Download the Identity Center SAML metadata file and certificate. Your app needs both to set up the trust.
  4. Optionally set the application start URL, relay state and session duration.
  5. Under application metadata, enter the app’s ACS URL and SAML audience, then submit.
  6. Add the SAML attribute mappings your app needs, then assign users or groups on the application’s details page.

AWS recommends assigning groups rather than individual users. Nested groups aren’t supported, so a user who belongs only through a nested group can see a message saying they have no applications. Identity Center doesn’t validate signatures on incoming SAML authentication requests, and an app that supports only OpenID Connect can’t use it.

Two catches

The first catch is that you can’t script the setup. AWS’s CreateApplication API and the matching CloudFormation resource, AWS::SSO::Application, only create OAuth 2.0 customer managed applications. AWS says SAML 2.0 customer managed applications are created in the console only. Schmidt’s team runs everything else as infrastructure as code, so its dev and prod apps were clicked together by hand.

The second catch is the session. The admin app keeps a signed cookie, checked in a CloudFront Function. Removing someone in Identity Center stops new sign-ins, but an existing session lasts up to 7 days. Schmidt says that’s fine for two people. Identity Center passes the session duration to the app in the SAML assertion, and AWS says each app decides whether to treat it as a maximum or an exact length. In Schmidt’s setup, the cookie lifetime is the window.

Two catches: SAML apps are console-only, and an existing session cookie can outlive removal by up to 7 days
SAML apps are console-only, and a session cookie keeps working after someone’s removed.

Sources


Discover more from Sulat AI & Tech News

Subscribe to get the latest posts sent to your email.