New answers tagged

0

The suggestions mentioned in the comment didn't work for us. So, instead of defining username in UserBuilder, we added a method with below code that is getting called from our Login Action - string userName = $"{Context.Domain.Name}\\{userId}"; Sitecore.Security.Accounts.User virtualUser = AuthenticationManager.BuildVirtualUser(...


0

Here the response from Sitecore support: According to the investigation performed, the App.MapWhen cannot be used in this method, since it implies direct interaction with OWIN middleware and bypasses federated authentication layer. Thus, implementation of your desired functionality would require a lot of customization and, unfortunately, falls out of scope ...


1

You are missing the code in SecurityTokenValidated event to call ApplyClaimsTransformations, it needs to include something like this (make sure to keep your other code there too: private Task OnSecurityTokenValidated(SecurityTokenValidatedNotification<OpenIdConnectMessage, OpenIdConnectAuthenticationOptions> context) { TransformationContext ...


1

This answer isn't mine but posting in case anyone may need in future. As per @Nehemiah from Sitecore slack: Nehemiah: I don't think so. I believe they are part of middleware where Sitecore context won't be there. I followed the link mentioned by @Jeroen. https://sitecore.stackexchange.com/a/26878/3632 One small adjustment I had to make was, I assigned the ...


Top 50 recent answers are included