>
> And before you start paying for alternatives, please check out Azure B2C
> as I mentioned and see if it will do what you need. I’m constantly
> fascinated by projects where I see people buying tools that they already
> have a usable tool.
>
Oh yeah! I always like to use pre-supplied stuff befo
And before you start paying for alternatives, please check out Azure B2C as I
mentioned and see if it will do what you need. I’m constantly fascinated by
projects where I see people buying tools that they already have a usable tool.
For each Azure AD user (and I presume you already have some), y
It's been a few years now and it's a bit hazy ... but I only wanted to use
the authentication feature and had no need for fine-grained control over
who could call which API methods. You either authenticated into the app, or
not. I was led into all these configuration screens to register API details
Hi Greg,
I’m interested to understand why you think that “geared towards APIs” is a bad
thing. I understand that the first thing developers typically want to do is
authenticate users so that they can open the front door and get in the app.
However, this is meaningless if you don’t then use the
Thanks everyone, I'll go off and do the research now. If I make any
startling discoveries in coming weeks I'll report back in case it helps
others attempting SSO.
*GK*
P.S. I did try Auth0 about 4 years ago, but it was so over-featured and
geared towards "APIs" that I couldn't identify the possib
If it is a corporate app and in Azure - just go to the App Service and turn
on Easy Auth. One Click. Job Done. We use it everywhere and it is great.
If it is for a large number of users, then follow the advice of others on
this thread.
David Connors
da...@connors.com | M +61 417 189 363
Telegram:
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,
HiIt'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
The easiest way is to use Auth0 (https://auth0.com/). It costs, but will
save a lot of hair.
On Mon, Apr 26, 2021 at 8:59 AM Greg Keogh wrote:
> Folks, we have some old apps with their own simple credentials databases
> containing user, password, login count, permissions, etc. They're classic
>
Hi Greg,
I’d suggest, for a start, taking a detailed look at Azure AD B2C.
Presuming you already have Azure AD for some other purpose, this might be just
what you need. Most of these modern auth providers make it easy to use a
variety of alternate login methods.
Check out some videos on it, bu
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 conveni
11 matches
Mail list logo