MaiklT
commented
4 years ago Obviously a change in the logic: 1) "Enable Auto Login" must be activated to take the IP-Address range into account 2) If a client can't automatically login, it is not considered as anonymous, but gets a login-popup (from the Windows server, not a DNN Login)
After changing the IP-Address range and excluded the IP addresses of the WAF and the transfer domains, everything works fine.
I upgraded a site from DNN 7.4.2 to 8.0.4 (on the way to go to 9.4+).
The settings for the AD Provider are:
Enabled: [X] Hide Login Controls: [ ] Synchronze Role: [ ] Synchronze Photo: [ ] Enable Auto Login: [ ] Do Not Automatically Create Users: [ ] Enable Debug mode: [ ] Provider: ASDIAuthenticationProvider Authentication Type: Delegation Root Domain: dc=intra,dc=local Username: DOMAIN\Username Password: ** Email Domain: @somewhere.com Default.domain: intra.local Auto-login IP Address (Optional): 10.0.0.1-10.255.255.255 Allowed Serch Bots: gsa-crawler;MS Search 5.0 Robot
There are users that are not domain members, they access the intranet site via a WAF, and are not authenticated in the intranet. That is OK, and worked fine in 7.4.2 (and before).
After the upgrade, it did not auto-login the users from the internal IP addresses anymore. I activated the "Enable Auto Login" checkbox, and it worked again, but now, these external users can't login anymore. I need a quick solution to fix that, any ideas?