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

I had this issue and realized I had forgotten to set my model to IEnumerable after upgrading my project to GlassMapper 5+ with Sitecore 10.1 @model IEnumerable Edit attempt 3: @model IEnumerable<GlassBase>


1

I believe your approach is wrong. I once tried something similar, and using args.App.MapWhen directly is not supported as per Sitecore support, see more here. This is how I have seen this work: Remove the args.App.MapWhen and use same UseOpenIdConnectAuthentication for each site Inside the RedirectToIdentityProvider set the correct OIDC options for the ...


2

Other option to install it is to override the Sitecore 10 files with Sitecore 10.1 files. Looks like just files were changed in Sitecore 10.1 release. From my point of view is much more simpler to install a vanilla of 10.1, upgrade your NUGET packages to use 10.1 version and deploy it on vanilla solution.


2

Besides following the Sitecore upgrade guide, in order to upgrade SXA you should follow the SXA upgrade guide on the page https://dev.sitecore.net/Downloads/Sitecore_Experience_Accelerator/10x/Sitecore_Experience_Accelerator_1010.aspx The section "2.2.4 Remove obsolete module content" is reffering to old sitecore modules which are obsolete, for ...


0

Follow the instructions and use this guide Upgrade guide to Sitecore 10.1 Use Sitecore 10.1.1 artifacts and update your sitecore in all app service instances in Azure. Basically you use 10.1.1 files but use 10.1 upgrade guide, since 10.1.x doesnt have breaking changes there for you use 10.1 upgrade guide.


Top 50 recent answers are included