@johnmiller It looks like the issue is that the 'retrieve a user via JWT' functionality was removed in 1.60.0. (It appears the User API JWT authentication method was deprecated in version 1.50.0. An issue has been filed to remove it from the client libraries.
Thank you from bringing this to light.
@rachel-flatt OK, it looks like your application is using the JWT setttings from the Tenant. You can go to the Admin UI select Tenants -> Find the tenant your application is under -> Select Edit and go to the JWT tab. You should find the settings there.
@johnmiller Can you please share a code snippet of the call? I will try to recreate and see if we can figure something things out.
@patrick_ag Is this just when you are loading the page or are you trying to take some action?
@rachel-flatt It is odd that you do not see the page. Are you an admin user? Can you post a screenshot with what you do see? (Please be sure to redact secrets and private information)
@brad sounds super frustrating.
I'll send you a message.
@oliver-muthusami hmmm. I did some poking around Microsoft's documentation and found this.
The inclusion of the refresh token in the response can depend on several factors, including the specific configuration of your application and the scopes requested during the authorization process. If you expect to receive a refresh token in the response but fail to, consider the following factors:
Scope requirements: Ensure that you're requesting the offline_access scopes along with any other necessary scopes.
Authorization grant type: The refresh token is provided when using the authorization code grant type. If your flow differs, the response can be affected.
Client configuration: Check your application's settings in the identity platform. Certain configurations may restrict the issuance of refresh_tokens.
Are you sure you have Entra configured correctly?
@oliver-muthusami Awesome that you got what you need. Thanks for reaching out and letting us know!