Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Identity UI experience issues on SPA apps #9403

Open
ryanbrandenburg opened this Issue Apr 15, 2019 · 2 comments

Comments

Projects
None yet
3 participants
@ryanbrandenburg
Copy link
Member

ryanbrandenburg commented Apr 15, 2019

Found during verification.

  1. Identity UI pages have a footer, but SPA apps do not.
  2. Identity UI NavBar does not contain non-auth links, but Home/Counter/FetchData pages do.
  3. The link to the Privacy page in the footer of an Identity UI page actually points to the current page.
@ryanbrandenburg

This comment has been minimized.

Copy link
Member Author

ryanbrandenburg commented Apr 18, 2019

  1. When deployed to an Azure App Service the register and login links are not removed once you login, and there are console errors in the browser
HTTP500: SERVER ERROR - The server encountered an unexpected condition that prevented it from fulfilling the request.
(Fetch)GET - https://angularauthtest.azurewebsites.net/_configuration/Angular
  1. Needed to change the bitness of the publish profile to x86 before it would work as a self-deployed app.
@ryanbrandenburg

This comment has been minimized.

Copy link
Member Author

ryanbrandenburg commented Apr 18, 2019

All of the above were from testing Angular.

For React on Azure App Service the "Could not load settings" error seems to be even more pronounced as it seems to totally prevent Registration or Login. That one seems pretty bad, @mkArtakMSFT to re-prioritize as he sees fit based on this new info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.