6 Results for Category Authentication

In a multisite environment with Azure B2C for login, we were tasked with persisting a user’s login across sites. The plan to accomplish this involves determining when we’re linking to another site in a link provider, appending and passing (securely) the current logged in user when linking over, and determining when we’re coming from another site in a request pipeline.

Sitecore 9 makes it really easy to incorporate federated authentication into the admin panel. A large portion of the process simply involves a few configuration changes. Included as a part of these configurations are the group-to-role transformation mapping. The ease of these changes are nice, however adding a new role requires configuration changes, which means a deployment or (at the very least) an outage of the site. I recently incorporated federated authentication (via Okta) into a system, and was irked by this requirement. This subsequently drove me to add some logic to allow the group-to-role mappings to be configured within Sitecore.

Learn how to extend Insite to allow for changeable usernames. Out of the box, Insite doesn't allow users to change their username, because the username is used in matching users in integration jobs, and in the base business object's audit trail. This blog investigates a work around for making it seem as if a user can change their username.

In some cases, we might have a need to transfer user accounts between different Sitecore instances that do not use the shared user accounts storage. In this article, I would like to share my experiences and thoughts on how I completed a successful migration...

In my previous article Authentication using OpenID Connect in a Sitecore application, I have discussed the steps involved in configuring the Owin Katana Middleware. This article outlines on how we use consume this configuration to authenticate extranet anonymous users in a Sitecore MVC application using ClaimsIdentity...