Sign-in problem with Composer 2.1.2 - Githubissues

microsoft / BotFramework-Composer

Dialog creation and management for Microsoft Bot Framework Applications

https://docs.microsoft.com/en-us/composer/

MIT License

869 stars 372 forks source link

Sign-in problem with Composer 2.1.2 #9508

Open alivascu opened 1 year ago

alivascu commented 1 year ago

Issue:

Upon logging into Azure subscription, getting AAD error AADSTS54005: OAuth2 authorization code was already redeemed, please retry with a new valid code or use an existing refresh token."

Bot Composer version:

2.1.2

Steps towards reproduction:

Open Bot Composer
Login to Azure
Close Bot Composer and shut down machine for a whole day.
Start the machine
Open Bot Composer
Login to Azure again

Actual result:

We get a message with the above error from the login process.

Expected result:

That we are able to login to Azure without an issue.

Troubleshooting done:

Opened Bot Composer in debug mode, and from the data it appears that the refresh token has expired Eg SubError: token_expired V2Error: invalid_grant AADSTS70043: The refresh token has expired or is invalid due to sign-in frequency checks by conditional access. The token was issued on 2023-02-07T14:26:48.9112799Z and the maximum allowed lifetime for this request is 43200.

anishprasad01 commented 1 year ago

Hi @alivascu,

I'm not able to reproduce this issue on 2.1.2 when signing into Composer using an account joined to the Microsoft Azure tenant.

Have you tried a fresh reinstall of Composer or trying a nightly build?

HugoDurana commented 1 year ago

Good morning Anish,

Hope this finds you well.

Please be advised that I am the one who has asked @alivascu to open up the ticket. Indeed I did try to reinstall Composer, went as far as removing any and all cached files for the application under the AppData Folders (both Local and Roaming) ones, but to no avail. I am willing to test a nightly build, but I will need your help in locating said builds.

You can also ping me internally on Teams.

Best regards, Hugo Durana

HugoDurana commented 1 year ago

Not working in current machine (non-domain joined) with the latest nightly.

HugoDurana commented 1 year ago

Second test made on another machine that is also not domain-joined, I was prompted to add the application to the domain and selected "No, just sign-in to this app only".

That worked, even though I got a "Can't go there from here" message.

johnataylor commented 1 year ago

@HugoDurana are you still having sign in issues? Also, we wondered whether your sign in issues specific to Composer? Because customers have reported losing the ability to sign into different services at the same time. This might help us drill into this. Thanks.

HugoDurana commented 1 year ago

Good morning @johnataylor

Thank you for reaching out. Yes, I am still experiencing issues regarding signing-in. Both @anishprasad01 and myself had a session the other day where I demo'ed the issue to him.

Feel free to ping me internally for this.

HugoDurana commented 1 year ago

Hello @johnataylor

Tried with the latest nightly build, and still getting the same exact error message.

anishprasad01 commented 1 year ago

Linking another issue regarding authentication: https://github.com/microsoft/BotFramework-Composer/issues/9516

Error codes are varied, but common points include:

AD domain-joined machines
Enterprise AD accounts
Clearing caches, Identity folders in AppData, and installing the nightly do not appear to work.