AAD multi-tenancy is ideal for medium-to-large enterprises who own and manage their own identity infrastructure. This sample is for small enterprises, usually without their own identity infrastructure. It provides support for an application that needs to group it's users into discrete groups, each representing an application tenant.
This sample implements an Azure Function App, which uses Azure KeyVault to sign OAuth2 client assertions used to obtain JWT tokens from Azure AD. The private key used to sign the client assertion and thus authenticate the function to Azure AD is generated in the KeyVault and never leaves that service (it is not exportable).
Premier Dev Consultant Marius Rochon shares an example of a PowerShell script to upload a set of B2C IEF policies to one or more B2C tenants.
Premier Dev Consultant Marius Rochon explores OAuth2 questions you need to ask and how the answers lead to the selection of the grant.
The OAuth2 specifications define six different grant types (https://tools.ietf.org/html/rfc6749 and https://tools.ietf.org/html/draft-ietf-oauth-device-flow-15). Each provides the most optimal (from the security point of view) way of obtaining access or (for OIDC) id_tokens given the circumstances of the client application.
Following up on a previous blog post, Premier Developer Consultant Marius Rochon describes recent changes and compares the use of Azure AD multi-tenant features with the custom features in B2C.
Read Marius’s first post here.
Since then, there have been some changes to the demo application regarding new modes and new features.
In this post from his blog, Premier Developer consultant Marius Rochon provides a demo application that illustrates how to use Azure Active Directory B2C for authentication in a multi-tenant application.
The ‘regular’ Azure AD has build-in support for multi-tenant applications. In that case,
This post on authentication and authorization is from Premier Developer consultant Marius Rochon.
Claims list included in the ClaimsPrincipal usually originate from the security token received by the application as part of user authentication (SAML, OpenIDConnect id token) or access authorization (OAuth2 bearer access token).
Check out this blog from Premier Developer consultant Marius Rochon for information on how to integrate ASP.NET applications with CA Siteminder.
A customer was having a problem integrating an ASP.NET application with CA Siteminder v12.52. Firstly, there was a problem with using SAML2.0 token formats.
In this post, Premier Developer consultant Marius Rochon shares his application authentication experience in order to help you create your own Multi-tenant WebAPI applications.
The VS.NET 2015 wizard for adding authentication to ASP.NET WebAPI projects does not support using the multi-tenant option.
Here’s a quick read from Premier Developer consultant Marius Rochon’s blog. In it, Marius gives some great reasons to leverage passive authentication protocols in your applications rather than writing your own code to handle credentials.
Some time back I wrote about avoiding handling of credentials (creation/maintenance/verification of user names,