Chrome App Config Blocking Sign-In Pop-UpsSolved

Participant
Discussion
1 day ago Mar 26, 2026

Hey, we’ve configured Chrome via app configuration with a URL blocklist (BlocklistURL), along with settings like homepage, home button, and default search engine. 

We’re seeing a strange issue — any website that requires a sign-in pop-up (authentication prompt) is getting blocked when the blocklist is configured. 

A couple of things we noticed: 

  • If we remove the blocklist → sign-in pop-ups work fine 

  • If we just remove specific URLs from the blocklist → those sites load, but the sign-in pop-up is still blocked 

  • The pop-up only starts working again if we completely delete the app configuration and reapply it 

Also, this setup works fine in other MDMs..the issue seems to happen only with Hexnode. 

Is this expected behavior or are we missing something? 

Replies (2)

Marked SolutionPending Review
Hexnode Expert
23 hours ago Mar 26, 2026
Marked SolutionPending Review

Hey @zayn, when Chrome app configuration is pushed, authentication prompts may get blocked if authentication schemes are not explicitly defined. Even if the blocklist is not configured, applying the app configuration can result in Chrome treating the allowed authentication schemes as empty. This means that authentication methods such as ntlmbasic, digest, and negotiate are not permitted, which prevents the sign-in pop-up from appearing. 

To resolve this, configure the option Supported authentication schemes within your app configuration, setting its value as “basic,digest,ntlm,negotiate”, each separated by commas.   

This explicitly allows all commonly used authentication methods and restores the sign-in pop-up behavior. 

Marked SolutionPending Review
Participant
10 hours ago Mar 27, 2026
Marked SolutionPending Review

Thanks for the help!

Save