- UI type: Angular
- DB provider: Oracle
- Identity Server Separated (Angular): yes
My abp project is an Identity Server Separated, but I want to merge them together to not go to the Identity Server and come back afterward. I mean disabling Identity Server and writing manually my own token endpoint and UI components(or other way). Which steps I should follow?
Can you explain more of your intentions? Do you already have a separate identity server project with your business code in it and you decided not to use a separate IdentityServer? Or is it about the login page only that you want to host login pages in your angular instead of redirecting back to IdentityServer?
Do you already have a separate identity server project with your business code in it and you decided not to use a separate IdentityServer?
In my project initially, you go to the identity server, if you successfully logged in, the identity server handles generating token(or whatever it is) in a different port and comes back to the base URL again. It is a simple application I do not want this complexity. I want to write an API to generate a token and assign it wherever needed.
There is a solution for this problem on YouTube in MVC projects but not in Angular.
When you are using the non-separate Angular template, IdentityServer library is embedded to Http.Api.Host project (backend) instead of a different runnable project.
You can create a new non-separate Angular template and move your business code to the new project. Or you can examine and compare the non-separate template with your current template and move the IdentityServer to Http.Api.Host.
If your application doesn't require to be modular, you can also try the single-layer template with angular UI.