Unable to login to AWS through LEAPP

[captechno-kbanks]

Login to AWS through LEAPP doesn't complete the connection/create Session:

1. Open LEAPP
2. Start Session OR Login (have tried both)
3. Authorization requested window = Confirm and continue
4. Sign in "User" (accepted)
5. Sign in "Password" (accepted)
6. MFA Code - Allow access (accepted)
7. Request approved window is different this morning, see attached. I believe this has been a window with an "OK" button previously.
8. Last window "Authoriataion requested / AWS user code for this SSO request is "-"" and hit OK
9. Result = Login & Start Session Failed

Have attached:

• Login & Start Session failed.PNG
• Request approved window.PNG

Details:

Leapp Version	0.25.2
SsmPluginVersion	1.2.398.0
Platform	win32
Awscli	aws-cli/2.4.17 Python/3.8.8 Windows/10 exe/AMD64 prompt/off

[cdelcastillo]

Have you updated the authentication method to In-browser?

1. Right click your SSO integration and select edit.
2. Update Auth. method to In-browser.
3. Click on Edit integration.
4. Try login again.

This worked for me. See #545 for more.

[francbartoli]

I have the same issue, I can confirm that the problem is only related to the in-app configuration

[captechno-kbanks]

I am now doing the authentication through the browser where previously I had it set to “in App”. Have been using the in App authentication since the time of install and setup, over a yr. now. What was different about logging in when it broke was the previous day I closed my PC (which puts it in auto hibernate I believe) and the following morning is when I ran into this – fyi Didn’t do anything else out of the norm, but I’m up and running now, thank you for responding. Keith Banks – Software Solutions Specialist CapStone Technologies LLC (402)-804-0815 From: Francesco Bartoli ***@***.***> Sent: Thursday, March 21, 2024 10:43 AM To: Noovolari/leapp ***@***.***> Cc: Keith Banks ***@***.***>; Author ***@***.***> Subject: Re: [Noovolari/leapp] Unable to login to AWS through LEAPP (Issue #546) I have the same issue, I can confirm that the problem is only related to the in-app configuration — Reply to this email directly, view it on GitHub<#546 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANPQNQQVFMHFEBBTEORUNHTYZL5X5AVCNFSM6AAAAABE7QGAH2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJSG4YDGMZXGA>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[francbartoli]

@captechno-kbanks it was already captured here

[ericvilla]

#540 (comment)