Identity product manager at GitHub - @hpsin. I own the Apps and Authorization platforms. Previously Microsoft Identity protocols PM for Entra and the Microsoft Account systems.
There's a legitimate engineering issue here too that bears mentioning.
Your marketing team will charge ahead with migrating all your product.business.com sites to just product.business
You'll get half a year into that migration before someone asks about shared domain cookies. Oh, login.business.com dropped an SSO cookie on business.com?
After that you'll get the lovely request - you work with the browser people, can't we just edit the standard to drop a cookie on a TLD?
Heya. I own Microsoft Oauth2. We use JWTs for our access tokens. (the consumer service uses encrypted tokens, yes).
Auth0 just championed the RFC for a standard for JWTs as access tokens too, largely informed by the architect there working on our access token format.
CAEP and RISC are how we're tackling revocation. Encrypted JWTs handle PII.
Oauth is a fantastic way to scale complexity - the whole "first party" consideration here is a red herring. Do you think we want Outlook calling the Exchange backend via a different auth protocol from the one we tell 3p clients to use? That's a waste of time to go build.
We also just added support for the JWTs emitted by Google and AWS, so that you can token exchange their JWTs for an access token in our ecosystem.
BFF is not great for long term security, notably token binding. It's hard enough to bind an artifact to the browser session from the IDP - having each app implement binding passthrough from browser to app to IDP is even worse.
Clients are either public or confidential. Confidential clients have a registered credential (cert, secret) that's used to prove that eg your server backend is actually your server backend.
Ha, thank you, I was about to inject the pro-Cleveland piece mentioned in your link, so that was educational. How bounteous our country is to have so many second place cities!
It certainly seems true of a breed of MBA. When interviewing candidates for PM it's interesting to see the breakdown in people who care about how the product works and those who consider it a widget to be put in a box. "Bring the customer demands to the eng team (without providing a useful translation)".
Google does this at 10/hour as well. Unsure of others. Both Google and Microsoft match cash donations too up to 15k/year - it's a wonderful perk to have after you've basically covered all your living expenses and savings etc. I can eg fund a minor scholarship at half cost, or direct serious money to a cause I care about.
Can confirm, this is popular on my team. Additionally, this should also direct actual dollars to OSM - volunteering for an organization is matched in cash by Microsoft, to the tune of 20-something an hour.
Which is odd because Github doesn't use Teams, they're Slack based. As in, if I set up a meeting with my Github counterparts they're late because they had to install Teams.
I mean, no, but they do let you sign in with a non Gmail address. (My @microsoft.com is a consumer Google account. Same way my @gmail personal email is a consumer Microsoft account.)
Means of contact end up being a pretty useful way of organizing identities (phone numbers have their issues) and having ways to fix mistakes. The one thing I haven't seen solved in web3 is communication to a user. Easy enough to encrypt messages in ipfs though, I suppose.
Speaking to this myself - I was blown away by Masterclass letting me do this, after I forgot it would renew. I responded to their "hey you've been charged" email with something like "I forgot about this and didn't mean to renew". In perhaps ten minutes I had a cancelation notice and refund.
Way more likely to get their stuff again. Bonus points for not sending the bill from some faceless "no reply" address.
Or when the politician in question releases an edited video and "NFTs" it or signs it with their DID. Then you're just back to trusting a consensus of trusted media disagreeing with them.
Password authentication to something running on local network (and therefore can't get a useful TLS cert) is about it, in my experience. Use the PAKE in place of TOFU to trust a self-signed TLS cert in the browser and get rid of cert warnings, since in my understanding PAKE also helps authenticate the server, not just the user.
We've largely broken app architectures in AAD down to spa, hybrid, and "webapp". Where webapp means "a server owns the state, and creates a web page and sends it to your browser". MPA is rough - 110% some engineer within minutes of that doc going live will point out that their spa has multiple pages.
Personally, I like TWA - will start using that locally to see how it goes. Look for a doc update near you soon...
The AZs are generally spaced far enough apart to withstand this. While rumor was that this is specifically done with your scenario in mind, it may also be a happy coincidence for grid and other infrastructure resilience.
The eye is very calm - and freakily bright. It glows from all directions as the light is reflected down into it, causing all the windows in the house to cast shadows onto the floor, which your brain can quickly realize is wrong!
But I expect on the water it's a bit different - I experienced the eye of hurricane Charley when it made landfall in Florida in 2004. My uncle actually ran for his camera because he figured it'd be calm a while. Thankfully he was right
This varies immensely by the product team. If you file a bug on the AAD protocol docs I have a self-enforced SLA of a business day (or less). And a CVP enforced SLA to solve it in 30 days. And I generally love the folks who do file bugs - they're engineers, and usually fairly savvy.
Other teams do get burnt out on docs though, especially when customers use them for abuse or free architecture help. My favorite was someone asking me how to use an Oracle product. I know our branding is confusing but it's not that bad... Is it?
Which gets you back to the problem OP has - trusting that device enough to make it a secure root of trust. Windows lets you do it, so do Android and iOS. But your admin, maybe not (or you're not on windows, which is more likely I guess).
Hm, that's surprising. I added it as a known error response to the Internet Explorer dev tools in 2015 (inadvertently causing "I'm a teapot" to be localized into 108 languages...). I wonder what "support" means.
Credit tips are cashed out at the end of the day, generally speaking, so that the "credit tips" are offset by unreported "food cash payment" that sits in your pocket all night. (I believe it also relies on the business underreporting sales, but... Cash. Also likely hiring the wait staff under the table)
Was surprised to not see Chet's name come up. When we were shipping WSL, I got the team in touch with Chet to give WSL a test run, with no major surprises (a couple edge case bugs, IIRC). I'm bummed I never met him in person while at Case, but always a fun little factoid that came in handy the one time.
Far from snark, this certainly seems to reinforce the point. We have two levels of response, where one level is called in for more dire circumstances (life or death) and correspondingly has equipment capable of handling a worse situation.
As an analogy - DNA is source code. The first arrow is the parser and creates RNA that is a reflection of the DNA. The second arrow (RNA to protein) is the compiler, taking the parsed code (RNA) and generating a program (protein) from it.
At no point is the source code consumed to create the program, akin to DNA.
Steps 2 and 3 are unrelated to the gallery. The gallery entry is basically a registered url that takes you to the app, to trigger a login (2) which triggers provisioning (3) in your tenant. So you can visit any app and add it to your tenant by signing into the app. Lots of folks want a gallery entry though, so that's what the docs focus on
Very much so the right person to ask! This is great to hear that there's a need for this. I think our mental model of a lot of enterprises is that "old code" stays SAML and new code (that isn't copy paste from old) is OIDC. If there's actual desire to migrate apps between the protocols, that's great. Can't promise easy though given the diversity of starting places. Thanks!