Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.
- ABP Framework version: v3.3.0
- UI type: Angular
- Tiered (MVC) or Identity Server Seperated (Angular): tiered
- Exception message and stack trace:
- Steps to reproduce the issue:
We are attempting to deploy our application (dev laptop version behave as expected) to our staging enviroment (single IIS site). xxx.HttpApi.host published and angular prod build but in wwwroot. The main issue currently is there is a disconnect on the auth server as when click login we get a 500 UNAUTHORIZED Client. We can manually navigate to /Account/login and login however most idenitity function don't work.
We configured environment.prod.ts changed the urls to match the qa enviroment. The app setting in HttpApi.host SelfUrl,ClientUrl and Authority urls all set to match the staging server url.
The other issue there is no log file being produced in logs so difficult to troubleshoot. (If we run it outside IIS with dotnet command line the log is created)
We do find information on deployment scenarios (with where the configuration is for each) for the commercial version?
UPDATE: We have seperated the HttpApi.host and angular to seperate IIS sites and adjusted the url settings of each. The site now loads and we can login however we have noticed a few strange expierences,
- The redirect login takes extremely long, over 60 seconds, using self signed certs so unsure of cause.
- When we deploy the hostapi app IIS often gives us ANCM error and we need to reconfigure the app pool, but don't really change the config, never expierences with dotnot core deployments before. 3 if the system is redirected to some of the error pages (not in angular but the identity pages, xxx/Error) the urls are wrong as they point to the url of the hosted idenity server, but that would not be the URL the user went to.
2 Answer(s)
-
0
Did you configure your Identity Server in the database tables. Check out the tables with the prefix
IdentityServer. EspeciallyIdentityServerClients,IdentityServerClientRedirectUris,IdentityServerClientPostLogoutRedirectUris -
0
Did you configure your Identity Server in the database tables. Check out the tables with the prefix
IdentityServer. EspeciallyIdentityServerClients,IdentityServerClientRedirectUris,IdentityServerClientPostLogoutRedirectUrisDear Alper,
Please be more specific, what I should configure, the documentation says nothing about this, and there is no documentation regarding this, I have been trying to publish the system for todays now! I copied the same local database to production, but even that did not work!, now I get the new error named: (UNAUTHORIZED_CLIENT)
