ION V1 was announced today. ION is used in a decentralized identity network to be able to help resolve for example decentralized identifiers and find their public keys. This is one of the core differences with a traditional Identity Provider where you always need to go to the well-known endpoint to retrieve the location of the public keys and download the public keys there to see if the signatures of the tokens are correct.
The other day I was trying to troubleshoot an issue where I needed to know what the content of an ID token coming from AAD was for a mobile application. The application was setup to use code flow with PKCE and using fiddler to troubleshoot this didn’t work since AAD is protected with SSL pinning so trying to have fiddler be the man in the middle didn’t work out. It helped me figuring out what request was sent to the server but not the content of the response.
In short, you can access your UDM Pro with https://unifi.local and make the security warning go away. I have been using my unifi hardware for some time at home now and I love it. The one thing that kept being annoying is accessing the cloudkey software over SSL. It always returning this warning: And if you approved and continued you still got this icon in your browser: I was reading Scott Helme’s blogpost how to setup SSL.
We have been delivering developer training on the Microsoft Identity platform around the world. We finally managed to hit the studio and get some of these recorded. One of the big changes we made over time is to steer away from protocol details more towards concepts and APIs. It’s like why explain how NTFS works while you only want to write a file to disk with an API. The entire series from me and my colleage Kyle Marsh are worthwhile watching.
Today I started a new job. I am still working in Azure Identity as Program Manager. Still working in CxP (Customer and partner experience), but moving back to the @Scale team (they work with ISVs, Partners, SIs to get our Identity platform adopted at scale). I am going to work on DID or Decentralized Identities. Helping onboarding our partners to make sure we successfully get market adoption of this brand new technology.
This has caused me a ton of confusion and my customers keep getting confused as well. Azure Active Directory has been around for some time now. Some time ago we added a new endpoint (V2) which is more standards compliant and supports both AAD and MSA accounts and for example features like incremental consent. Still people get confused about our numbering scheme and I totally understand why. Let me try to explain a little bit how this all works.
The other day I needed a test application to try something with SAML support in Azure Active Directory. I started looking how to configure an ASP.NET Core webapplication to support SAML. It’s very easy to set it up for OIDC authentication but I found out ASP.Net (core) doesn’t support SAML out of the box. Google to the rescue and ignoring the blogpost from my colleague Christos (he’s wrong, it’s WS-Fed not SAML he’s using in his blogpost) , I found a few 3rd parties who build support for ASP.
One of my machines was giving me a headache. I could not connect to my Synology file shares. All my other machines in my could just fine except this machine. Even after a reinstall it didn’t work. I kept getting the error: The specified server cannot perform the requested operation. The difference between the machines working and not working was the machine not working was Azure Active Directory Joined. The other machines weren’t.
Wow that’s the longest blogpost title I have ever used. Hopefully this will help finding this page if you are searching for a solution I am describing here. One of our customers came to us with a question how to integrate our B2C product with Realm Cloud. I had looked at this product before but didn’t know what technically was possible for integration with B2C. The request was to use B2C tokens with the custom JWT Authentication Realm cloud supports.