Sign-in error code 50173

Question

Failure reason

The provided grant has expired due to it being revoked, a fresh auth token is needed. The user might have changed or reset their password. The grant was issued on '{authTime}' and the TokensValidFrom date (before which tokens are not valid) for this user is '{validDate}'.

Additional Details

Expected part of the token lifecycle - either an admin or a user revoked the tokens for this user, causing subsequent token refreshes to fail and require re-authentication. Have the user sign-in again.

Answer 1

Thank you for the reply.

Unfortunately, none of these resolutions apply or work.

There is no conditional access policy applied.

User has reset their password 3 time now.

Account has been active since its creation.

Grant has never been revoked by Admin or User.

I've tried everything I can. Still no results.

Sign-in error code

50173

Failure reason

The provided grant has expired due to it being revoked, a fresh auth token is needed. The user might have changed or reset their password. The grant was issued on '{authTime}' and the TokensValidFrom date (before which tokens are not valid) for this user is '{validDate}'.

Additional Details

Expected part of the token lifecycle - either an admin or a user revoked the tokens for this user, causing subsequent token refreshes to fail and require re-authentication. Have the user sign-in again.

Answer 2

This solution worked for me.

https://forum.uipath.com/t/office-365-scope-fresh-auth-token-required-after-password-reset/232750/9

Answer 3

Hello @Tom Flanagan ,

The error message indicates that the provided grant has expired due to it being revoked, and a fresh auth token is needed. This error message is highlighted in our Azure AD Authentication and authorization error codes documentation.

There might be couple of possible scenarios in this case.

1. This error is due to refresh token expiry either if the password changed for the user or the token has been revoked either by user or admin through PowerShell or Azure portal.
2. There might be chance that Conditional Access policy has been configured to control user
   Refresh token and force user to sign-in again.
3. Another possibility which is highly unlikely is Refresh token expired due to inactivity for more than 90 days.

To resolve this issue, you can follow the below steps:

Ask the user to sign in again to get a fresh auth token. This will help to resolve the issue in most cases.

1. Check if the user has changed or reset their password. If yes, then the user needs to use updated the password in Azure Active Directory (Azure AD) to get a new auth token.
2. Check if the grant has been revoked by an admin or a user. If yes, then the user needs to request a new grant from the admin or the user who revoked the grant.
3. You can also check the Azure AD sign-in logs to get more information about the issue. The sign-in logs provide detailed information about the sign-in events, including the status, error codes, failure reasons and if any Conditional Access Policy is being applied. You can use this information to troubleshoot the issue further.

I hope this helps and hence would request you to please "Accept the answer" if the information helped you. This will help us and others in the community as well.