Hi Min Yong, Here is a link to the Demo code: github.com/kevinrjones/settingupduendeidentityserverwithEntityframework - I have also added the demo code to the description for future viewers.
I'm having a lot of trouble with the DB contexts. Do you no longer need an explicit context for the PersistentGrantContext and the ConfigurationGrantContext? Are they already baked into the "add operational store" and "add configuration store" methods in builder.Services? And if so, how do you extend them to override OnModelCreation and OnModelConfigure?
Amazing content, thank you for every minute of it. I was just thinking, is there any chance for you to create a similar series of videos where you will be focusing more on implementing authentication and authorization of a user via a mobile application and how the redirects work when using a public client such as a mobile application? Thank you once more, really helpful stuff. :D
Hi Marko, Thank you for the kind words, will pass this onto the team and we will discus and see if if that is something we can create in the future. Thank you again for your thoughtful feedback :)
The passwords are typically stored as a one way hash in an identity database. Lots of solutions use ASP.NET Identity schema. However you can store the password where ever you like, IDS is a framework for providing OAUTH/OIDC protocols. Authentication is your own logic. As for per user authorization, no this is not a role for IdentityServer. We have an authorization engine which you may like to consider called Enforcer (www.identityserver.com/products/enforcer).
I have a problem - If my access token expired, it returns a 401 which is correct, but it does not redirect back to the login, how can I have it return back to the login screen of identity server (this is now in my homecontroller) - currently its just throwing the exception because the "result.IsSuccessStatusCode" is not true.
@@identityserver Ok thanks, I have one more question. In architecture like this that you created, where I should store user data (registering users) should I create different aspnet identity microservice or should I put it in to IdentityServer via creating new controller and different db (or use ids db?)?
Thank you for the series of tutorials. I did three of them, including part1, par,t2, and this part. My questions: 1- In this video the program.cs doesn't need Config.cs, so where does the Duende Identity Server get scopes, "webapi.read" and "webapi.write" and client names "m2m_client" and "Interactice_client"? 2-In the GitHubub repository of the WeatherMvc project in "appsetting.json", the"ClientPassword": "511536EF-F270-4058-80CA-1C89C192F69A", and "ClientSecret": "49C1A7E1-0C79-4A89-A3D6-A37998FB86B0", are the values that don't work ( 401 error), but "ClientPassword": "SuperSecretPassword" and "ClientSecret": "SuperSecretPassword" work.
You are a hero Kevin. Thank you for such easy walk through!
This was a great 4 part series, I hope you will continue it with more parts.
your channel is always great for coding
I just set this up last week. It was a real challenge. Sure could of used this demo then, lol! Thanks for the video. Cheers
Another great Demo - thanks a lot!
please add code link to description (it is in the end of a video)
If you got an error "No DbContext named 'ConfigurationDbContext' was found." you have to build the project first.
solved all my issues
Be nice to have the link in the video description and not just at the end of the video.
Hi Min Yong, Here is a link to the Demo code: github.com/kevinrjones/settingupduendeidentityserverwithEntityframework - I have also added the demo code to the description for future viewers.
@@identityserver Thanks so much! Great content btw!
I'm having a lot of trouble with the DB contexts. Do you no longer need an explicit context for the PersistentGrantContext and the ConfigurationGrantContext? Are they already baked into the "add operational store" and "add configuration store" methods in builder.Services? And if so, how do you extend them to override OnModelCreation and OnModelConfigure?
Amazing content, thank you for every minute of it. I was just thinking, is there any chance for you to create a similar series of videos where you will be focusing more on implementing authentication and authorization of a user via a mobile application and how the redirects work when using a public client such as a mobile application?
Thank you once more, really helpful stuff. :D
Hi Marko, Thank you for the kind words, will pass this onto the team and we will discus and see if if that is something we can create in the future. Thank you again for your thoughtful feedback :)
In this Architecture, Where does the Password stored for identity server to validate the user ? Also, Can we maintain authorization in Duende ?
The passwords are typically stored as a one way hash in an identity database. Lots of solutions use ASP.NET Identity schema. However you can store the password where ever you like, IDS is a framework for providing OAUTH/OIDC protocols. Authentication is your own logic.
As for per user authorization, no this is not a role for IdentityServer. We have an authorization engine which you may like to consider called Enforcer (www.identityserver.com/products/enforcer).
how do I replace jwt token with reference token? any video for that?
I have a problem - If my access token expired, it returns a 401 which is correct, but it does not redirect back to the login, how can I have it return back to the login screen of identity server (this is now in my homecontroller) - currently its just throwing the exception because the "result.IsSuccessStatusCode" is not true.
remove the cookies from your ui project
Hello how can I persist data in MongoDb? Is it even possible in this version? I cant find any working solution (.net6, duende is, mongo)
Hi
I've not actually used it but there is a nuget package available that may be what you need
www.nuget.org/packages/AspNetCore.IdentityServer.Mongo/
@@identityserver Ok thanks, I have one more question. In architecture like this that you created, where I should store user data (registering users) should I create different aspnet identity microservice or should I put it in to IdentityServer via creating new controller and different db (or use ids db?)?
Thank you for the series of tutorials.
I did three of them, including part1, par,t2, and this part.
My questions:
1- In this video the program.cs doesn't need Config.cs, so where does the Duende Identity Server get scopes, "webapi.read" and "webapi.write" and client names "m2m_client" and "Interactice_client"?
2-In the GitHubub repository of the WeatherMvc project in "appsetting.json", the"ClientPassword": "511536EF-F270-4058-80CA-1C89C192F69A", and "ClientSecret": "49C1A7E1-0C79-4A89-A3D6-A37998FB86B0", are the values that don't work ( 401 error), but "ClientPassword": "SuperSecretPassword" and "ClientSecret": "SuperSecretPassword" work.
first :P