Problem with saml when enable GLOBAL_LOGIN_REQUIRED

[lopmuj]

Describe the issue
I got a problem when enable the saml and set GLOBAL_LOGIN_REQUIRED = True

the following access log shown as below

web-1            | [pid: 51|app: 0|req: 160/247] 172.26.0.2 () {58 vars in 3401 bytes} [Thu Sep 11 17:17:16 2025] GET /accounts/login/?next=/accounts/login/%3Fnext%3D/accounts/login/%253Fnext%253D/accounts/login/%25253Fnext%25253D/accounts/login/%2525253Fnext%2525253D/accounts/login/%252525253Fnext%252525253D/accounts/login/%25252525253Fnext%25252525253D/accounts/login/%2525252525253Fnext%2525252525253D/accounts/login/%252525252525253Fnext%252525252525253D/accounts/login/%25252525252525253Fnext%25252525252525253D/accounts/login/%2525252525252525253Fnext%2525252525252525253D/accounts/login/%252525252525252525253Fnext%252525252525252525253D/accounts/login/%25252525252525252525253Fnext%25252525252525252525253D/accounts/login/%2525252525252525252525253Fnext%2525252525252525252525253D/accounts/login/%252525252525252525252525253Fnext%252525252525252525252525253D/accounts/login/%25252525252525252525252525253Fnext%25252525252525252525252525253D/accounts/login/%2525252525252525252525252525253Fnext%2525252525252525252525252525253D/accounts/login/%252525252525252525252525252525253Fnext%252525252525252525252525252525253D/accounts/login/%25252525252525252525252525252525253Fnext%25252525252525252525252525252525253D/accounts/login/%2525252525252525252525252525252525253Fnext%2525252525252525252525252525252525253D/robots.txt%252525252525252525252525252525252525253F488218 => generated 0 bytes in 3 msecs (HTTP/1.1 302) 9 headers in 1639 bytes (1 switches on core 1)
web-1            | 172.26.0.2 - - [11/Sep/2025:17:17:16 +0700] "GET /accounts/login/?next=/accounts/login/%3Fnext%3D/accounts/login/%253Fnext%253D/accounts/login/%25253Fnext%25253D/accounts/login/%2525253Fnext%2525253D/accounts/login/%252525253Fnext%252525253D/accounts/login/%25252525253Fnext%25252525253D/accounts/login/%2525252525253Fnext%2525252525253D/accounts/login/%252525252525253Fnext%252525252525253D/accounts/login/%25252525252525253Fnext%25252525252525253D/accounts/login/%2525252525252525253Fnext%2525252525252525253D/accounts/login/%252525252525252525253Fnext%252525252525252525253D/accounts/login/%25252525252525252525253Fnext%25252525252525252525253D/accounts/login/%2525252525252525252525253Fnext%2525252525252525252525253D/accounts/login/%252525252525252525252525253Fnext%252525252525252525252525253D/accounts/login/%25252525252525252525252525253Fnext%25252525252525252525252525253D/accounts/login/%2525252525252525252525252525253Fnext%2525252525252525252525252525253D/accounts/login/%252525252525252525252525252525253Fnext%252525252525252525252525252525253D/accounts/login/%25252525252525252525252525252525253Fnext%25252525252525252525252525252525253D/accounts/login/%2525252525252525252525252525252525253Fnext%2525252525252525252525252525252525253D/robots.txt%252525252525252525252525252525252525253F488218 HTTP/1.1" 302 0 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36"

To Reproduce
Steps to reproduce the issue:

1. successfully integrated SAML login
2. set GLOBAL_LOGIN_REQUIRED = True
3. See error

Expected behavior
The login page should be shown

Screenshots

[mgogoulos]

Hi, this doesn't help much, can you do a tail -f logs/* and see if there's an error? Also describe the steps in more details in order to see what has worked and where the error might be

[lopmuj]

Hi, there is nothing printed out in the log. It shows only the access log.
I have added more logs from Chrome.
When I press the Enter key on the URL, it displays this log.

[Brets0150]

I ran into this exact issue yesterday and was able to resolve it. I had set up my server with Azure Entra ID SAML authentication. When I enforced global login and disabled local user login, I encountered a redirect loop — the system kept redirecting between the homepage and the login URL.

The root cause appears to be that, with global login required and local login disabled, Django attempts to redirect users to the default local login page. Since that login method is unavailable, users are bounced back to the homepage, triggering the same redirect logic again — resulting in a loop.

To fix this, I specified the correct SAML authentication URL in my local settings. Here's what I did:

1. My "Login Option" URL configured for EntraID in MediaCMS:
   https://<MyDomainName>/accounts/saml/mediacms_entraid/login/

2. Added the following line to ./deploy/docker/local_settings.py:
   LOGIN_URL = "/accounts/saml/mediacms_entraid/login/"

This change ensures Django uses the proper SAML login route, effectively breaking the redirect loop and allowing authentication via EntraID as intended.

[lopmuj]

Thank you :)

[mgogoulos]

thanks for the insights @Brets0150 !

It would be great if you can open a PR with changes in the /docs suggested how you have setup this in details!

[Brets0150]

PR sent