Last post Apr 20, 2015 09:45 AM by Ziklo
Apr 17, 2015 03:44 AM|Ziklo|LINK
I`ve an Asp.net web app running in Azure. It was working ok, I was doing authentication with Azure Active directory, and everything was right. Login, administrator view, logout, etc. After Holidays the key of the app was expired, so I created new one and
everything got messsed up.
The situation now is the following. I can login to the published web, but it does not difference between administrator and users, I was managing this with Azure Active directory users and groups. The logout is giving error. If I try to view my web in private
browsing it launches an error.
In localhost is working fine, it differences between admin and users, it does the logout correctly, etc.
For the localhost web app I've a differente app in azure active directory, but I`ve been comparing and all the routes are ok.
I don´t know where to change things, or why the app is having so messy behaviour. I don´t understand how web.congif file is working, and when is taking into account its parameters (localhost or published).
Any suggestions are wellcome!!
Apr 19, 2015 11:17 PM|Will shao - MSFT|LINK
Form your description, It seems that your users and roles is disordered. But base on my experience, when the key was expired, some refresh token can be used to re-authenticate the user. I am not sure the token was refreshed. So firstly, I recommend you
can refer to those scenarios for Azure AD:
Secondly, if you want to try refresh the token, I suggest you can try this document:
At last, I am not sure that you whether used Graph API into our project. If you used it, I think you can try to get all of your users information and roles to confirm that which stage is wrong into your project.
Any further information, please let me know.
Apr 20, 2015 09:45 AM|Ziklo|LINK
Thanks for your reply.
I`ve read the links but don´t see anything that can help me. The key is that it is working fine in localhost, signing in AZure AD, but the published versión is not working. I also have a native app that is calling webApi incorporated in the asp.net web,
and the same occurs, when working in localhost everything is ok.
am I missing something when I publish the app? something I have to change in the manifest or in the web config?
Thanks for you time!