I've added a new post on my blog here: https://sitecore.derekc.net/extending-sitecore-identitys-sitecore-profile-to-map-additional-profile-data/. Summary below:
So three steps to add a field that exists in UserProfile to Sitecore:
Add the field to sitecore.profile in Sitecore Identity
Create a claim transform in Sitecore Identity
Map the claim in Sitecore
I cannot give you a detailed answer but you should know that in the future (not yet scheduled) the AD module will be retired and Sitecore will move away from the Microsoft Membership model and towards Microsoft Identity. This introduces support for the Microsoft.Owin authentication middleware. This can be used as a replacement for the AD module.
I heard from Sitecore support on the roles at least, so I wanted to share this answer:
The concept of the Federated Authentication means that you delegate
authentication to a trusted identity provider and all the users are
managed on the side of this provider. Based on this the User Manager
usage is not intended to maintain users from aside ...
Yes, you need to set loginPage attribute of shell site to $(loginPath)shell/SitecoreIdentityServer/IdS4-AzureAd.
This will redirect /Sitecore/Login or /Sitecore to AzureAd login page directly
Here is patch config-
<?xml version="1.0" encoding="utf-8" ?>
<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/" ...
I found that there is a configuration setting that can be enabled which runs the preview mode with the currently logged in user (an authenticated user) instead of the default/anonymous user.
It's called Preview.AsAnonymous, and setting this setting to false will allow users to preview as the currently authenticated user instead.
Source: USING AN ...
Raised a ticket with Microsoft to look into the issue. They have got their back-end team to look into the issue, and the investigation result seems that something in Azure platform didn't worked as expected, that caused the issue to happen.
Their back end team has now made the relevant changes to get the functionality working now.
From what I can see, you are probably using Sitecore 9.0 or 9.1. Based on that assumption, your implementation is not correct.
For Sitecore 9.0 and 9.1, you should used federated authentication to let endusers login. We use the OpenID Connect protocol and WSFed to connect external identity providers to Sitecore. From what I understand, that is the same ...
Assuming you have configured federated authentication properly. You can do this by mapping claims.
This is an excerpt an example from @Bas Lijten 's blog.
As the Administrator role isn’t a real role, but more a Sitecore user
property, this “role” needs to be set in a different way. The
Propertyinitializer can be used to achieve this. First, it ...
On the documentation there are the following items:
When you configure and use Azure AD with the Sitecore Identity server,
you have to remember:
Check the ID tokens checkbox in the Advanced Settings in the Web -
Authentication tab in the application registration.
Set the value of the groupMembershipClaims setting in the application
manifest to ...
I have a different scenario where I use 2 Azure AD groups to claim a single Sitecore Role, and it look like this
<AzureADToAuthor type="Sitecore.Plugin.IdentityProviders.DefaultClaimsTransformation, Sitecore.Plugin.IdentityProviders" >
<!-- Group 1 -->
<Claim1 type="groups" value=&...
Not much of an answer, but I can say that this has been confirmed as a bug. As of Sitecore version 9.2, this is still unresolved.
I just followed up, and there is no official bug reference for this. If encountered, the best action would be to go via Sitecore Support.
I faced a similar issue and i came across this post which resolves the current issue:
Could not find configuration node: federatedAuthentication/sharedTransformations/setIdpClaim
Note: There might be other issues. This answer solves the issue you have mentioned above.
Incase the post disappears here is the answer (use this instead):
You have to use owin.cookieAuthentication.signedIn pipeline.
There are a bunch of fedauth-related pipelines (like owin.cookieAuthentication.*) defined in the \App_Config\Sitecore\Owin.Authentication\Sitecore.Owin.Authentication.config file that you might want to explore.
It could certainly be done, but it'll require some hand tooling.
Aside from the articles linked by @Vinicius you should take a look at Create an ASP.NET web app with Azure Active Directory B2C sign-up, sign-in, profile edit, and password reset. This talks about using B2C in a regular .NET web app - which is essentially what we're talking about, since ...