question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Multiple MFA prompts for chained profile (still)

See original GitHub issue

Describe the bug Re-creating as #182 was closed without resolution.

I have two active sessions, one I’ll call master and one I will call chained. master requires MFA. chained inherits MFA from master.

When my mfa token expires, I am prompted twice. Entering my MFA token in either of the prompts works equally well to authenticate, and the other prompt can be canceled (albeit an error is displayed upon canceling; this seems to have no effect).

Leapp Version 0.12.2

To Reproduce Steps to reproduce the behavior:

  1. Create an AWS session (in my case an IAM User) with MFA called master.
  2. Create a chained role session (IAM Role Chained), using master as root.
  3. Activate both sessions (which should only require MFA once iirc).
  4. Wait for expiry
  5. Notice that you are prompted for MFA reauthentication twice.

Expected behavior A single prompt for MFA token.

The logical link between master and chained already exists in Leapp configuration, and only the master session is actually declared to need MFA, so Leapp ought to be able to infer that they are asking for the same token, and only ask me/perform the operation once.

Desktop (please complete the following information):

  • OS: OSX
  • OS Version 11.6.7
  • Leapp Version 0.12.2

Issue Analytics

  • State:open
  • Created a year ago
  • Reactions:1
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
andreacavagna01commented, Nov 3, 2022

We will add a single modal to solve the issue.

1reaction
ericvillacommented, Aug 4, 2022

Hi @jcogilvie, the actual behavior does not take into account the fact that another MFA prompt modal, related to the same IAM User session, is already spawned and is visible to the user. To solve this, we could add a logic that checks whether the IAM User-related MFA modal is currently active or not; if yes, the second session flow should wait until a new IAM User session token is available. Does it make sense to you?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Azure AD Multi-Factor Authentication prompts and session ...
Multiple prompts result when each application has its own OAuth Refresh Token that isn't shared with other client apps. In this scenario, MFA...
Read more >
Excessive MFA? : r/sysadmin - Reddit
Multiple MFA prompts throughout the day for the same user is probably excessive in most cases. I'd be curious to see the threat...
Read more >
Lapsus$ and SolarWinds hackers both use the same old trick ...
Methods include: Sending a bunch of MFA requests and hoping the target finally accepts one to make the noise stop. Sending one or...
Read more >
Why do I keep seeing MFA prompts? - Okta Support
Examine policies to ensure that the user(s) do not have a policy applied that could enforce repeated MFA prompts. Investigate the sign on...
Read more >
What is Two-Factor Authentication (2FA) and How Does It Work?
Two -factor authentication is a form of MFA. Technically, it is in use any time two authentication factors are required to gain access...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found