I am experimenting with Windows Azure Active Directory. In a client (desktop) application the user enter his credentials and authenticate to access a REST service. I\'m usin
I captured the calls to Azure Active Directory (AAD) with Fiddler and found a JSON response that included the access_token, expires_in and expires_on, id_token, refresh_token, resource, scope and token_type (Bearer).
The expires_on equals 1398790050. So I went to Wolfram Alpha, queried how many seconds this was after 1970 and added 2 hours (I'm in the UTC+2 time zone). The access token is valid for 1 hour. In the TechNet forums it is mentioned the expire token is valid for about 80 days.
Yes, the Refresh Token does expire.. I am not sure, but I believe you can set the TTL or expiration of the token in the setup of the WAAD properties on azure. I have to check, but I am not where I can access Azure at the moment.
I implemented the Azure AD SSO on mobile apps and used ADAL Nuget package. I had few queries from my clients on the expiration of the refresh-token. After going back and forth with Azure Engineering team, and trying few things, here are my findings. I have documented the details in a blog post here:
Full details can be found in this blog post
Solution is here.
tokenRefreshExtensionHours
It is now configurable through App Service's Resource Manager to configure tokenRefreshExtensionHours.
"using Resource Explorer to manage your site’s auth settings, you can add a setting named “tokenRefreshExtensionHours” to {site}/config/authSettings.properties and set it to the number of hours to allow an expired token to be used for refresh. "
Thanks to cgillum.
The refresh token expiration time now can be configured officially : https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-configurable-token-lifetimes