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.
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 @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.
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.
@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?
@saintpoida hello,
Exceptions thrown in the Identity Server endpoint (at least when its a separate endpoint, i have not tested a combined solution yet) seem to just be blank screens, im not sure if that is a bug or if its expected behaviour?
If you mean you can only check the error via logs but can't see a friendly error on UI about backend traffic, it is default behavior of identityserver logging. I am guessing it's high probably because of security concerns.
@vishalnikam hello,
Can you elaborate your problem please? As I've read, you wanted to integrate your Angular app to Azure AD or Identity Server 4 but then you want to remove IdentityServer from angular template.
Do you have an external identityserver other then abp application provides that you want to connect your Angular app to?
If you want to integrate your angular app to AzureAD, you can define a new client for your angular app in the identityserver with implicit flow and alter the authentication of angular app. This link may help: https://damienbod.com/2016/03/02/angular2-openid-connect-implicit-flow-with-identityserver4/
On Frontend, Administration-> IdentityServer-> Clients -> Actions -> Edit
Can you verify both of your clients has Require Consent not selected and Allow Remember Consent option is selected?
If than, can you also verify in database of your project in table IdentityServerClients, your both clients have RequireConsent value equals to 0 and AllowRememberConsent equals to 1?
Can you give more information about your project setup? .Net Core MVC/Angular, which version, tiered or not etc?