Being able to decrypt the OWIN AuthenticationTicket can be very useful. In the cases where the cookie/tickets are shared across applications, this is especially true.
Interestingly, if you’re using OWIN for both cookie-based authentication and access tokens, the Ticket is stored in both mediums.
With that in mind, the easiest method to decrypt a ticket to access claims, etc is to simply stand up a protected Resource server with a single Api endpoint to display the contents of the ticket. Going this route, the decryption is automatically handled by OWIN with very little code. The endpoint can be accessed by a user’s browser (decrypting the cookie) or by a server passing in a Bearer token.
With my previous endeavors using OWIN Middleware for an SSO Authentication system, I used DotNetOpenAuth as the client to make the OAuth Authorization Code grant flow. However, after a bit of research, I’ve learned that hooking into the OWIN Middleware can completely eliminate the need to use DotNetOpenAuth.
Additionally, eliminating DotNetOpenAuth and its dependencies makes creating a Nuget reusable package for the applications that I intended to use with the SSO/OAuth2 mechanism much simpler.
Adding custom claims in .NET Identity, through OWIN, or otherwise is pretty straight forward.
But, what if we want to step outside of, or augment, the OAuth flow?
Earlier today, after a system outage, I was sent a W3C IIS Log to take a look at.
After staring at this log for a few minutes in Notepad2, my eyes started to glaze over. Basically, staring at system or IIS logs with a text editor is useless if there are tons of events or requests.
I knew there are plenty of parsing tools out there for log analysis, and I had used some before. Unfortunately, I had none of these tools installed on my laptop. Googling quick lead me to a Microsoft tool called ‘LogParser’ that I had never heard of before.
I’m still playing with Azure and getting a full fledged application working and hosted using the Azure services. As I showed yesterday, setting up a Web App is pretty easy.
The next step for me involves moving an Entity Framework Database using Migrations to Azure.
With all of the hoopla lately about Azure, I have been playing with it, and Application Insights, for the past few weeks.
One thing that I hadn’t really delved into is its .NET Web App hosting. As an MSDN subscriber, many of the cloud services are offered in some form of free capacities. This includes Web App and Azure SQL hosting.
Let me preface this by stating that I’m a noob when it comes to node. This really is my first time diving into its feature set.
Microsoft Ignite is coming to a close and it’s been a whirlwind week for me.
Overall, the material presented adhered to Microsoft’s agenda of touting Azure, its cloud, and IaaS/PaaS products. Infrastructure as a Service and Platform as a Service are interesting, in and of themselves, but I find that most aren’t ready to jump in with both feet.
Another day of the Microsoft Ignite conference has passed. I felt more productive this day than I had during the first day. But, there have been bumps along the way.
I attended various sessions with topics ranging from Identity/Security to simple Angular/SPA apps to Microsoft’s new Threat Analysis tools.