AnswerBun.com

Why Content Delivery in Sitecore 9.3 is treating users as editors?

Sitecore Asked by Johnny Lopez on December 7, 2021

After upgrading to Sitecore 9.3, some times, users are not able to log in to Content Delivery (using ADFS) because we’re exceeding the maximum editor’s restriction by license. It’s weird because is Content Delivery. The error I’m seeing in logs is:

The maximum number of simultaneously active (logged-in) editors exceeded. The User extranetxxxx cannot be logged in to the system. The maximum of editors allowed by license is 10.

The user is then redirected to /sitecore/client/Applications/LicenseOptions/StartPage but is throwing 404 error, obviously, because it is Content Delivery site.

2 Answers

This is the support help I got and fixed it: Could you please try overriding the CheckDomainGuard processor using the following:

namespace CustomNamespace
{
    public class CustomCheckDomainGuard : Sitecore.Owin.Authentication.Pipelines.CookieAuthentication.SignedIn.CheckDomainGuard
    {
        public CustomCheckDomainGuard(BaseLog log) : base(log)
        {

        }

        public override void Process(SignedInArgs args)
        {
            if (string.Equals(args.Site.Name, Sitecore.Constants.ShellSiteName, StringComparison.Ordinal))
            {
                base.Process(args);
            }
        }
    }
}

Then please use a patch file containing the following to patch it in:

<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/" xmlns:set="http://www.sitecore.net/xmlconfig/set/">
    <sitecore>
        <pipelines>
            <owin.cookieAuthentication.signedIn>
                <processor type="Sitecore.Owin.Authentication.Pipelines.CookieAuthentication.SignedIn.CheckDomainGuard, Sitecore.Owin.Authentication" patch:instead="*[@type='CustomNamespace.CustomCheckDomainGuard, CustomAssembly']" resolve="true" />
            </owin.cookieAuthentication.signedIn>
        </pipelines>
    </sitecore>
</configuration>

Answered by Johnny Lopez on December 7, 2021

Sitecore support has registered this a bug with reference number 366550, and there is a hotfix available for 9.2 and 9.3 here.

Answered by Joost on December 7, 2021

Add your own answers!

Related Questions

How to get General Link Field in RenderFieldArgs?

0  Asked on August 23, 2021 by gautam-aneja

 

Setting site default language in SXA

1  Asked on August 23, 2021 by mohamed-mosa

   

Sitecore domain and sub domain authentication

1  Asked on August 23, 2021 by suresh-r

   

No data recorded in Experience Analytics

3  Asked on August 23, 2021 by breno-diniz-pelosi

   

GraphQL query to search for pages based on template

2  Asked on August 23, 2021 by serhii-shushliapin

   

Sitecore SxA Composite Layout not adding custom css and js

1  Asked on August 23, 2021 by nadine-lendzian

 

Sitecore Item URL with Custom Domain in Azure PaaS

2  Asked on August 23, 2021 by alok-kumar

   

Updated field in rendering variant not working

2  Asked on August 23, 2021 by barada-behura

   

Creating multi site using Sitecore JSS

1  Asked on August 23, 2021 by haappyy02

 

Scale Out Content Management AppService

1  Asked on August 23, 2021 by pirate-briggs

     

Use SXA rendering variant for dynamic object

1  Asked on August 23, 2021 by user2980

   

Custom Item Url Builder

1  Asked on August 23, 2021 by ethan-schofer

 

Ask a Question

Get help from others!

© 2023 AnswerBun.com. All rights reserved. Sites we Love: PCI Database, UKBizDB, Menu Kuliner, Sharing RPP