Login.config File

[Telfer, Will]

Currently on the majority of Baylor's Shibboleth SSO servers  (all are running version 4.2.1) only have the ldaps.config file pointing to Active Directory servers in Azure (which is also where the Shibboleth SSO servers are located). There are 2 pools that both have the login.config file that points ldap back to our on-premise Active Directory servers. Is the login.config file a legacy file that is no longer used or is it a backup to the ldap.config file if that connection cannot be made?

I could find references to the login.config file in the Shibboleth v2 & v3 instructions, but not for v4 (which is what we are currently running - 4.2.1 as mentioned previously). We are trying to assess the impact of a datacenter outage on our SSO environment & my understanding when I took over support was that we were no longer reliant on the datacenter for SSO, but this file discovery has me questioning that.

Thank You,
Will Telfer, M.S. (he/him/his)
Identity and Authentication Analyst
Information Technology Services

Follow BaylorITS & look for the #BearAware:
Twitter: @BaylorITS
Facebook: facebook.com/BaylorITS
Website: baylor.edu/BearAware

[cid:image001.png at 01DAEE58.1D5AE5C0]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20240820/c33cc646/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 2368 bytes
Desc: image001.png
URL: <http://shibboleth.net/pipermail/users/attachments/20240820/c33cc646/attachment.png>