Hi Greg This might be worth looking into https://workos.com/
I listened to https://softwareengineeringdaily.com/2021/04/05/workos-making-enterprise-ready-apps-with-michael-grinich/?utm_source=rss&utm_medium=rss&utm_campaign=workos-making-enterprise-ready-apps-with-michael-grinich On Mon, Apr 26, 2021 at 9:40 AM djones147 <djones...@gmail.com> wrote: > Hi > > It's fairly straight forward. You register on the provider sire and they > supply you with a token. This token you send when you ask for the remote > login. And then they redirect to a failed or successful login. > > So asp.net is fine you have a public return address. > > With wpf and the ilk you need to redirect to a page on the server and > store that success/fail code with an identifier then fetch that back with > the client later. > > Some providers don't send back a provided id. But you can fake this by > sending the success/fail to a different url for each user. Ex a different > route for each client. > > It's not hard to do at all, but can seem like you don't have a handle on > it until it all works. > > Hth Davy. > > > > Sent from my Galaxy > > > -------- Original message -------- > From: Greg Keogh <gfke...@gmail.com> > Date: 26/04/2021 00:59 (GMT+01:00) > To: ozDotNet <ozdotnet@ozdotnet.com> > Subject: Sign-in with social accounts > > Folks, we have some old apps with their own simple credentials databases > containing user, password, login count, permissions, etc. They're classic > old fashioned systems. > > Increasing numbers of apps let you sign-in with your Facebook, Google, > Microsoft, etc account these days. This is really convenient, and the > security burden is taken by someone else. > > How can our apps participate in a social sign-in option? Has anyone done > this? I imagine some terrible obstacles... > > ? Apps would have to be registered with the various various companies. > ? The client apps might be WPF, Xamarin, Blazor or ASP.NET, so how would > they hook into the sign-in process. > ? Each company might return different types of tokens or even follow > different conventions. > > *Greg K* >
