atmos auth list
Display all authentication providers and identities configured in your Atmos project. View authentication chains showing how identities assume roles through providers or other identities. Supports multiple output formats including interactive tables, hierarchical trees, JSON, and YAML for integration with other tools.
Usage​
atmos auth list [--format <format>] [--providers [names]] [--identities [names]]
Examples​
# List all providers and identities in table format (default)
atmos auth list
# Show only providers
atmos auth list --providers
# Show only specific providers
atmos auth list --providers=aws-sso,okta
# Show only identities
atmos auth list --identities
# Show specific identities
atmos auth list --identities=admin,developer
# Display as hierarchical tree
atmos auth list --format tree
# Export as JSON for programmatic access
atmos auth list --format json
# Export as YAML
atmos auth list --format yaml
# View authentication chains in tree format
atmos auth list --format tree --identities
Output Formats​
table
(default)Displays providers and identities in formatted tables with columns for key attributes. Shows authentication chains inline for identities.
tree
Hierarchical tree view showing providers and identities with nested attributes. Visualizes authentication chains clearly with parent-child relationships.
json
Machine-readable JSON output containing the complete provider and identity configurations. Useful for programmatic access and integration with other tools.
yaml
Human-readable YAML output of provider and identity configurations. Good for reviewing configuration or generating documentation.
Flags​
--format
/-f
Output format:
table
,tree
,json
, oryaml
. Default:table
.--providers [names]
Show only providers. Optionally filter by comma-separated provider names (e.g.,
--providers=aws-sso,okta
). Cannot be used with--identities
.--identities [names]
Show only identities. Optionally filter by comma-separated identity names (e.g.,
--identities=admin,dev
). Cannot be used with--providers
.
Understanding Authentication Chains​
Authentication chains show how identities authenticate through providers or other identities. Chains are displayed in the format:
provider → identity1 → identity2 → target
For example:
aws-sso → admin
- Direct authentication through AWS SSOaws-sso → base-role → admin-role
- Multi-step authentication with role assumptionokta → aws-dev → developer
- Authentication through Okta SSO, then assuming an AWS role
Chains can be arbitrarily long when using multiple role assumptions or identity federation.
Table Format Details​
Providers Table​
- NAME - Provider configuration name
- KIND - Provider type (e.g.,
aws-sso
,okta
) - REGION - Cloud region (if applicable)
- START URL / URL - Authentication endpoint
- DEFAULT - Marked with ✓ if this is the default provider
Identities Table​
- NAME - Identity configuration name
- KIND - Identity type (e.g.,
aws/assume-role
,aws/user
) - VIA PROVIDER - Provider used for authentication
- VIA IDENTITY - Parent identity for multi-step authentication
- DEFAULT - Marked with ✓ if this is the default identity
- ALIAS - Short alias for the identity
Tree Format Details​
The tree format shows hierarchical relationships with indentation:
Providers
├─ aws-sso (aws-sso) [DEFAULT]
│ ├─ Region: us-east-1
│ ├─ Start URL: https://example.awsapps.com/start
│ └─ Session
│ └─ Duration: 12h
Identities
├─ admin (aws/assume-role) [DEFAULT]
│ ├─ Via Provider: aws-sso
│ ├─ Chain: aws-sso → admin
│ └─ Principal
│ └─ arn: arn:aws:iam::123456789012:role/AdminRole
Related Commands​
atmos auth whoami
- Display current authentication statusatmos auth login
- Authenticate with a provideratmos auth validate
- Validate authentication configurationatmos auth env
- Export credentials as environment variables