SAML.to
  • Introduction
  • Installation
  • Configuration
    • Identity Providers
      • GitHub
    • Service Providers
      • AWS (Federated Roles)
        • Assuming Roles
          • AWS CLI
          • AWS SDKs
          • Docker
          • Terraform
          • Kubernetes
        • Adding Users
        • Adding AWS Accounts
        • Adding Roles
        • Roles for GitHub Actions
    • Configuration Reference
      • Substitutions
  • FAQs
  • Usage
    • CLI
      • login
      • assume
      • list-roles
    • GitHub Actions
      • Assume AWS Role Action
      • Config Sync Action
  • Advanced Usage
    • AWS
      • CloudWatch Dashboard Sharing
Powered by GitBook
On this page
  • Usage
  • Example Output
  1. Usage
  2. CLI

login

The login command is the primary command to store a user token from an Identity Provider (e.g. GitHub)

If no arguments are provided, it will assume a login is requested for GitHub.

Examples:

  • saml-to login

    • Functionally equivalent to saml-to login github

  • saml-to login github

    • Begins the process for a GitHub User Token and requests a user:email scope

Usage

saml-to login [provider]

Login to a provider

Options:
  --help       Show help  [boolean]
  --version    Show version number  [boolean]
  --provider   The provider for which to login  [string]
  --org        Specify an organization  [string]
  --withToken  Skip Device Authentication and save the provided token to ~/.saml-to/  [string]

Example Output

Following these commands, a browser window would be opened to begin the SAML Authentication flow.

saml-to login github

To continue, we need you to log into GitHub, and we will need the `user:email` scope to access your GitHub Identity.

Please open the browser to https://github.com/login/device and enter the code:

257C-5415


Token cached in: ~/.saml-to/github-token.json
Saved GitHub credentials to ~/.saml-to/github-token.json
PreviousCLINextassume

Last updated 2 years ago