Sign in with Identity Center
Authorise a session in your browser, and let Quorra keep it refreshed.
Quorra signs in to AWS IAM Identity Center itself, using the browser sign-in flow (authorization code with PKCE) that the AWS CLI also uses by default. You do not need the AWS CLI installed to sign in.
Sign in
Select a session in the sidebar and choose Sign In. Quorra opens your browser at the Identity Center portal. Approve the request there, and the browser hands the sign-in back to Quorra on your Mac; there is no code to type.
While a sign-in is in progress, the menu bar offers to reopen the authorisation page if you lost the tab.
If Quorra cannot receive the browser’s response on your Mac, it falls back to the device authorization flow: it shows a user code to confirm in the browser, and the menu bar shows the code and its expiry.
What expires, and when
Two different clocks matter, and the app shows both.
| What it is | What happens when it runs out | |
|---|---|---|
| Session token | The Identity Center token from signing in | You sign in again |
| Role credentials | Temporary credentials for one profile’s role | Quorra mints new ones, silently, while the session is still valid |
So a profile’s credentials expiring is routine and needs nothing from you. The session expiring is the one that asks you to sign in again.
Refreshing
Quorra refreshes the session token in the background while it remains valid. If a refresh fails, the session detail says so and offers Refresh now.
You can also sign in from the menu bar, from a profile that needs it, from a running endpoint whose served profile has gone stale, or from the command line:
$ quorra profiles sign-in ac:cp:org_admin
Signing out
Sign out on a session clears its token. If Quorra cannot reach AWS to invalidate the token remotely, it says so — the local copy is gone either way, and the token expires on its own within eight hours.