Hello @fish,
Can you be more specific about making AuthServer highly available?
@vishalnikam,
Hello, can you share related logs about identityserver? What is the exact problem do you come across?
Hello @gvnuysal,
Can you double check the Azure steps about registering the application? Selecting ID tokens, adding certificate and the azure client/tenant ids?
Also when you are switching between apps/azure etc; make sure clearing the browser storage (cookies). It may be related with it.
Hello, I think you checked the article about it already and understand why it can't be done directly by design.
However you can act like it by overriding the default Login Page and add a trigger method to javascript on window load to trigger that Azure Ad OpenId button whenever the page loading is done. Or Customize default Login Page and override login method to redirect to external signin.
Hello,
Page not found error is related with your azure settings. Meaning, Azure couldn't find related application to redirect to. Double check your ClientId and TenantId in appsettings.json are same with the ones on AzureAd.
Hello, There is an article about that could help: https://community.abp.io/articles/how-to-customize-the-login-page-for-mvc-razor-page-applications-9a40f3cd
Hello @hungvt,
It is related with your access token lifetime. Access Tokens used in frontend should have short life span and your application should be silently renewing it when required.
What is the point of using tokens instead of username/password if you'll keep it valid for 3 years, right?
Hello @chanchai-mwp,
Yes you can use IdentityServer as a single sign-on server, that's what it is made for :)
If you have angular application with separate identityServer, you can enjoy abp identityserver ui; try adding any client/api etc.
Hello @buaziz,
Thanks for the suggestion.
For all the apps, its good to have DbMigrator project dockerized. (Either let visual studio create a dockerfile for you or you can write your own)
For angular, there are 2 ways to dockerize. One of them is using caching and restoring npm packages inside container. Other one is building the dist outiside the container and only copy the dist in the dockerfile.
For non-tiered backend, you need to dockerize HttpApi.Host project. For tiered backend, you need to dockerize both HttpApi.Host and IdentityServer projects.
I hope it was helpful.
Hello @camping89@gmail.com,
Can you try clearing the cookies for chrome?
Just noticed, your app is not running on https; it should be running on https. Also if error persists, try pasting the auth application logs.
