nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Kerberos SSO broke after Chrome update

brancott

Hi, I'm running alfresco community 5.2.0 for many years now and everything was fine until recent Chrome 101.0.4951.54 release. SSO doesn't work anymore and entering login\password manually also doesn't allow to log in, Alfresco just keeps prompting for credentials.

Does anyone has the same problem? Is there any additional setting needed now?

Find more posts tagged with

Alfresco Content Services

Comments

ARC1

Thank you for posting this. I am having the same exact issue but never realized that it was a Chrome update issue. Oddly, I tried logging in with IE (which no one is using anymore) and SSO worked.

When we first setup Alfresco, SSO never worked with Edge even though it is based on Chomium now. Chrome worked after whitelisting our domain using the following register setting...

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome]
"AuthNegotiateDelegateWhitelist"="*.companydomain.com"

There was a registry fix for Edge to whitelist the domain, but it never worked.

Do we have to Whitelist the domain in a different setting now?

ARC1

Update:

Found that Google has changed the AuthNegotiateDelegateWhitelist to AuthNegotiateDelegateAllowList. I updated the registry but even though there are articles that say it fixed the issue, I have been unsuccessful using this fix.