@thomas Clark This is exactly what I was looking for and need help putting together. Question for you sir, how would you go about setting up a registration page? I'm assuming Identity Server doesn't handle registration and that would be all custom. Would you be able to do a video showing a setup like this with third party login like google or github?
Yes the registration page and associated code behind logic would need to be implemented. You could use the user auto provisioning logic as part of the external login process to create a user in IdentityServer when a user logs in via an external identity provider for the first time.
@@tnc1997 Do you know if there is any examples of the auto provisioning logic with third party login? I'm having a lot of trouble navigating identity server documentation. I'm sure all the information is there but there docs site is so poorly designed. its hard to find what your looking for.
@@funkel1989 you can find an example of the auto provisioning logic here: github.com/DuendeSoftware/IdentityServer.Quickstart.UI.AspNetIdentity/blob/4492007dc7a7637f5577eccf5a6bce942b0950bb/Pages/ExternalLogin/Callback.cshtml.cs#L110-L171.
@@tnc1997 One more thing. I followed your tutorial here to create this and the only difference between my repo and your repo is that i used vuejs 3 instead of react. I noticed that the .well-known/openid-configuration page is unable to be obtained. do you have any idea what to do to get it back?
@thomas Clark Why don't you create a series of video just to educate people from your experience like how to create production ready api like which can have multi users and publicly accessible? That would be a high value content
Hi Thomas I just wanted to know your view about using clean architecture should we use that in our projects if not then please give some reasons Thanks
Hi Thomas. I find your videos on IdS incredibly helpful. Thank you. Would this solution work if all three apps were deployed on the same domain but separate subdomains? I'd like my sign up/sign in SPA to be hosted separately from the the IdS.Bff but not sure if that will work? Like for ex. setting identityServerOptions.UserInteraction.LoginUrl = ";
No worries @@tnc1997. In that case, how would you deploy your current solution into a cloud env? Assuming you'd have to keep the UI and BFF together on the same instance given the relative paths. Or would it be easier to simply embed the SPA into the BFF and have it deployed as a single solution.
I would probably embed the SPA into the IdentityServer application such that they are running together as a single application: learn.microsoft.com/en-us/aspnet/core/client-side/spa/intro.
Looks like the sample solution here is probably pretty close to what it should look like: Git hub - /DuendeSoftware/Samples/tree/main/IdentityServer/v6/UserInteraction/SpaLoginUi (Linking directly to git hub deletes my comment)
Thansk for answering, I did implement this it redirected to google was able to authenticate to google but when doing the callback and managing the sign-in on the backend via `httpContext.SignInAsync` it doesn't do authenticate the user after redirection. Also there is no error 😂 weird. Do you have anyway reference for this scenario
Thank you for great video! Please create more videos!
Glad you liked it!
@thomas Clark This is exactly what I was looking for and need help putting together. Question for you sir, how would you go about setting up a registration page? I'm assuming Identity Server doesn't handle registration and that would be all custom. Would you be able to do a video showing a setup like this with third party login like google or github?
Yes the registration page and associated code behind logic would need to be implemented. You could use the user auto provisioning logic as part of the external login process to create a user in IdentityServer when a user logs in via an external identity provider for the first time.
@@tnc1997 Do you know if there is any examples of the auto provisioning logic with third party login? I'm having a lot of trouble navigating identity server documentation. I'm sure all the information is there but there docs site is so poorly designed. its hard to find what your looking for.
@@funkel1989 you can find an example of the auto provisioning logic here: github.com/DuendeSoftware/IdentityServer.Quickstart.UI.AspNetIdentity/blob/4492007dc7a7637f5577eccf5a6bce942b0950bb/Pages/ExternalLogin/Callback.cshtml.cs#L110-L171.
@@tnc1997 One more thing. I followed your tutorial here to create this and the only difference between my repo and your repo is that i used vuejs 3 instead of react. I noticed that the .well-known/openid-configuration page is unable to be obtained. do you have any idea what to do to get it back?
If possible would you be able to share a link to your source code repository so that I can take a closer look and see if I can diagnose the issue?
@thomas Clark Why don't you create a series of video just to educate people from your experience like how to create production ready api like which can have multi users and publicly accessible? That would be a high value content
Thank you for your suggestion, I will definitely consider that in the future.
Hi Thomas
I just wanted to know your view about using clean architecture should we use that in our projects if not then please give some reasons
Thanks
Hi, I am not familiar with clean architecture myself, so I wouldn't be able to comment on that.
Hi Thomas. I find your videos on IdS incredibly helpful. Thank you. Would this solution work if all three apps were deployed on the same domain but separate subdomains? I'd like my sign up/sign in SPA to be hosted separately from the the IdS.Bff but not sure if that will work? Like for ex. setting identityServerOptions.UserInteraction.LoginUrl = ";
Thank you very much! I haven't tested that scenario myself.
No worries @@tnc1997. In that case, how would you deploy your current solution into a cloud env?
Assuming you'd have to keep the UI and BFF together on the same instance given the relative paths. Or would it be easier to simply embed the SPA into the BFF and have it deployed as a single solution.
I would probably embed the SPA into the IdentityServer application such that they are running together as a single application: learn.microsoft.com/en-us/aspnet/core/client-side/spa/intro.
Looks like the sample solution here is probably pretty close to what it should look like:
Git hub - /DuendeSoftware/Samples/tree/main/IdentityServer/v6/UserInteraction/SpaLoginUi
(Linking directly to git hub deletes my comment)
Yes it's pretty similar to the sample in this video except that it uses vanilla JavaScript for the SPA UI.
This ka indeed helpful, how about exter. Authentication like google or Facebook how do we implement that?
You could create an endpoint in the .NET application that returns a challenge result that redirects to the external identity provider.
Thansk for answering, I did implement this it redirected to google was able to authenticate to google but when doing the callback and managing the sign-in on the backend via `httpContext.SignInAsync` it doesn't do authenticate the user after redirection. Also there is no error 😂 weird. Do you have anyway reference for this scenario
If you are able to share a repository with the source code then I would be more than happy to help!