[LON-CAPA-admin] Single Sign On

Neubauer, Paul pneubauer at bsu.edu
Sun Mar 21 18:01:04 EDT 2021

Hi Stuart,

Sorry. Yes it is odd. I did a screenshot instead of a text copy and then retyped the message from that. That's the cause of the "lonn-capa01" instead of "lon-capa01" (assuming you meant the double-n in "lonn" as what is odd).  (I also have to apologize for the HTML mail instead of plain text I think I've corrected both now.)

"lon-capa01.aws.bsu.edu" is the canonical name of the system (as we have it hosted on Amazon Web Services) and "lon-capa.bsu.edu" is an alternate name. So far, that has not been a problem.

Anyway, the file shibboleth2.xml.old is the (copy of the) original (which we have now reverted to) and shibboleth2.xml.new is the version of shibboleth2.xml that was in use when we got the error.

A diff of the two files:

diff shibboleth2.xml.old shibboleth2.xml.new
<             <SSO  entityID="http://shibboleth.bsu.edu/sso">SAML2 SAML1</SSO>
>             <SSO  entityID="http://federate.bsu.edu/sso">SAML2 SAML1</SSO>
<                             file="metadata/shibboleth.bsu.edu.xml"/>
>                             file="metadata/federate.bsu.edu.xml"/>

shows that the only changes were from shibboleth.bsu.edu to federate.bsu.edu and the result of the grep that I included in the original message showed that I changed all instances of the string 'shibboleth.bsu.edu'  so how did it get that the identity provider ought to be 'http://shibboleth.bsu.edu/sso'? There were no instances of that string anywhere in /etc (let alone /etc/shibboleth).. If the message had said that it was unable to locate identity provider (http://federate.bsu.edu/sso) I would be a lot less puzzled. 


From: LON-CAPA-admin <lon-capa-admin-bounces at mail.lon-capa.org> on behalf of Raeburn, Stuart via LON-CAPA-admin <lon-capa-admin at mail.lon-capa.org>
Sent: Sunday, March 21, 2021 4:55 PM
To: lon-capa-admin at mail.lon-capa.org <lon-capa-admin at mail.lon-capa.org>
Subject: Re: [LON-CAPA-admin] Single Sign On 
Hello Paul,

This line is odd:
"Identity provider lookup failed at (https:lonn-capa01.aws.bsu.edu/adm/sso)"

I would expect that to be lookup failed at:

IP address: points at lon-capa.bsu.edu
and lon-capa01.aws.bsu.edu has IP address:

If you see: "Unable to locate metadata for identity provider" the standard advice is to check the MetadataProvider element(s) in your shibboleth2.xml file.

Stuart Raeburn
LON-CAPA Academic Consortium
From: LON-CAPA-admin <lon-capa-admin-bounces at mail.lon-capa.org> on behalf of Neubauer, Paul via LON-CAPA-admin <lon-capa-admin at mail.lon-capa.org>
Sent: Sunday, March 21, 2021 2:30 PM
To: list about administration and system updating(lon-capa-admin at mail.lon-capa.org)
Subject: [LON-CAPA-admin] Single Sign On

Hi all,

We (Ball State University) are in the process of updating our identity provider. We are rolling in the changes so individual systems are being moved from using "shibboleth.bsu.edu" to using "federate.bsu.edu". It is lon-capa's turn.

I found all the files that referenced "shibboleth.bsu.edu" and copied them to a different location:

cp /etc/shibboleth/attribute-map.xml /root/sso/attribute-map.xml.old
cp /etc/shibboleth/shibboleth2.xml /root/sso/shibboleth2.xml.old
cp /etc/shibboleth/metadata/shibboleth.bsu.edu.xml /root/sso/shibboleth.bsu.edu.xml

I then made copies of the two .old files as .new and edited them to replace "shibboleth.bsu.edu" with "federate.bsu.edu"
I also got the new metadata (with wget  https://federate.bsu.edu/FederationMetadata/2007-06/FederationMetadata.xml) and saved it as federate.bsu.edu.xml

This morning I stopped shibd, copied the .new files to /etc/shibboleth/ and federate.bsu.edu.xml to /etc/shibboleth/metadata/

I checked for "shibboleth.bsu.edu":
[root at lon-capa01 ~]#  grep -H -r -i 'shibboleth.bsu.edu' /etc
[root at lon-capa01 ~]#
which shows that I had eliminated all references to it.

I restarted shibd and when I tried to log in, I got:

Unknown or unusable identity provider
The identity provider supplying your login credentials is not authorized for use with this service or does not support the necessary capabilities.
To report this problem, please contact the site administrator at security at bsu.edu.
Please include the following error message in any email:
Identity provider lookup failed at (https:lon-capa01.aws.bsu.edu/adm/sso)
EntityID: http://shibboleth.bsu.edu/sso
opensaml::saml2md::MetadataException: Unable to locate metadata for identity provider (http://shibboleth.bsu.edu/sso)

For some reason it was still looking for the EntityID http://shibboleth.bsu.edu/sso
I did a system reboot but got the same thing.

I reverted to the old files and we are working, but that will only last a couple of weeks before our cert expires for our old identity provider site and it goes down.

I am totally lost. is there somewhere else with shibboleth configuration data?


LON-CAPA-admin mailing list
LON-CAPA-admin at mail.lon-capa.org

More information about the LON-CAPA-admin mailing list