locked
Azure Mobile SDK - iOS User login expires after 1 hour RRS feed

  • Question

  • In our application we are using Azure Mobile SDK for iOS R3.4 on Client side and .Net code is deployed in App Service (IIS). We are using Azure Active Directory for authentication and authorization.

    On iPad native application, we are leveraging AAD call using SDK. Which challenges user to enter user name and password, generates Authentication Token along with Access Token and Refresh token. Currently app is working as described in URL

    https://docs.microsoft.com/en-us/azure/app-service/overview-authentication-authorization#authentication-flow 

    Issue is authentication token expires after an hour and we are forced to challenge user to relogin. Our Azure Active Directory team has extended Access token expiration time to 8 hours. When we call SDK feature to refresh token by calling .auth/refresh endpoint with Authentication token we are getting HTTP 401;

    Could you please help if SDK handles the refresh by itself or do we need to make any other configuration changes? Thanks for your help.


    vsudhakar

    Monday, January 20, 2020 4:30 PM

All replies

  • Any insights on this problem / issue are appreciated.

    In one of the link it is mentioned as Session default in AAD is 8 hours and can call refresh token after than till 72 hours as mentioned in below Microsoft URL

    https://docs.microsoft.com/en-us/azure/app-service/app-service-authentication-how-to#extend-session-token-expiration-grace-period<u5:p></u5:p>

    <u5:p></u5:p>

    But we don't see this behavior with our application. 


    vsudhakar

    Wednesday, January 22, 2020 4:18 PM
  • Thanks for asking question! After performing the initial investigations on the issue with the information you have shared and we feel that this requires a deeper investigation, so request you to send an email to AzCommunity[at]Microsoft[dot]com.

    Wednesday, January 22, 2020 5:34 PM
  • Thanks Sneha for your response. As suggested I sent an e-mail with issue details. looking forward for a response from Azure Community. 

    vsudhakar

    Thursday, January 23, 2020 8:52 PM