Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

googleapps: Introduce an option to set challenge preference while login #1388

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

hangpark
Copy link

@hangpark hangpark commented Jan 28, 2025

What's New

  • During login, you can set prioritized challenges as the primary method for GoogleApps MFA.
  • Specify the --google-challenge flag to choose a challenge type.
  • Use this flag multiple times to define the priority order of challenges.

Supported Challenges:

  • totp - Google OTP
  • ipp - SMS
  • dp - Device Push

Example (Multiple challenges):

$ saml2aws login --challenge=ipp --challenge=dp

In the command above, saml2aws first attempts to log in using ipp, then falls back to dp if ipp is not supported.

Example (Integration with 1Password):

If you use 1Password and have an item named Google stored in your vault, you can log in easily with the following command:

$ saml2aws login --force --challenge=totp --mfa-token="$(op item get Google --otp)"

For macOS:

The following conditions must be met:

  1. Install the op CLI tool:
$ brew install 1password-cli
  1. Install 1Password version 8 or later Download here.
  2. Enable CLI integration in the Developer settings of the 1Password app.

You can configure the 1Password app to unlock using biometrics, such as fingerprint authentication.

@hangpark hangpark force-pushed the google-apps-challenge-preference branch 4 times, most recently from 54a2bbb to d942a2e Compare January 29, 2025 06:21
**What's New**

* During login, you can set prioritized challenges as the primary method for GoogleApps MFA.
* Specify the `--google-challenge` flag to choose a challenge type.
* Use this flag multiple times to define the priority order of challenges.

**Supported Challenges:**

* `totp` - Google OTP
* `ipp` - SMS
* `dp` - Device Push

**Example (Multiple challenges):**

```bash
$ saml2aws login --challenge=ipp --challenge=dp
```

In the command above, saml2aws first attempts to log in using `ipp`, then falls back to `dp` if `ipp` is not supported.

**Example (Integration with 1Password):**

If you use 1Password and have an item named `Google` stored in your vault, you can log in easily with the following command:

```bash
$ saml2aws login --force --challenges=totp --mfa-token="$(op item get Google --otp)"
```

**For macOS:**

The following conditions must be met:

1. Install the `op` CLI tool:
  ```bash
  $ brew install 1password-cli
  ```
2. Install 1Password version 8 or later [Download here](https://support.1password.com/get-the-apps).
3. Enable CLI integration in the Developer settings of the 1Password app.

You can configure the 1Password app to unlock using biometrics, such as fingerprint authentication.
@hangpark hangpark force-pushed the google-apps-challenge-preference branch from d942a2e to a1759de Compare January 30, 2025 04:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant