@saintpoida,
What would be the best practise then to catch all the exceptions so I can wrap the relevant ones into User Friendly ones such as the password format when registering being incorrect. e.g if a user registers a new account with password of 'a' then thats invalid and they just get a blank screen on hitting register rather than a validation error.
Notice that user registration validation is related with Identity management, not IdentityServer. Hence it is not related with IdentityServer logging or exception handling. If user is trying to register with an invalid character and getting a blank screen instead of a validation error; you are right. There should be a user friendly exception to notice the user about that. Would you mind to create an issue about the problem with detailed reproduce steps on github?
Hello @arifharsono
AzureAD integration is done on MVC side. Angular frontend has different flows for authentication. Its currently on discussing about which flow to implement since Implicit Flow is deprecated. Angular Single SignOn (which also includes external login parties such as Azure AD) is on our roadmap with high priority. It will be implemented soon. (Probably at version 3.1 or 3.2)
You can still implement yourself. Maybe these links can help for implicit flow sample and authorization code with pkce sample.
Hello @robb,
Directly injecting the DbContexts will violate the Seperation of Concern principle. As much as it would seem to be a fast way to get things moving; it will cause more problems in the future.
Suggested way is to move this logic to application layer. You can inject different repositories from different dbcontexts and handle it on application layer. Then inject the application layer to Api or wherever else you want to.
I hope it was helpful.
Do you run redis server on containers?
Are all your redis instances on your dev machine that you are trying to connect via 127.0.0.1?
If they are on different machine, afaik you need to have static ip for Redis server and configure like public_ip:port.
Hello, it is pretty straightforward; here is a link from abp-sample repository BookStore sample injecting appService into api controller.
Keep on mind, when you implement your appService, you will already have api endpoints thanks to dynamic proxy. So you may not need to add anything to HttpApi. See aslo Auto API Controllers.
hello @wai,
I would consider adding a method to repository something like GetOrdersOfTheCurrentUsersAsync then calling it on application layer. Sample is here: https://github.com/abpframework/abp-samples/tree/master/OrganizationUnitSample#filter-entities-for-a-user
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.
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 @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.