Skip to:
Adding a comment inside of the <SSO> tag in shibboleth2.xml prevents login handlers from being added.
This <SSO> tag does add the appropriate handlers:<SSO entityID="https://idp.example.com/">SAML2 SAML1</SSO>
This <SSO> tag does NOT add the appropriate handlers:<SSO entityID="https://idp.example.com/"><
-->SAML2 SAML1</SSO>
When the comment is in the configuration file, I get the following error in httpd/native_warn.log when I try to sign in:
2011-02-04 13:42:20 ERROR Shibboleth.Apache [1772] shib_check_user: None of the configured SessionInitiators handled the request.
When the comment is not there, it works as expected.
When shibd is starting up and the comment is present, the SSO auto-configuration is not recorded in the log. That is, a line that looks like:
2011-02-04 13:42:19 INFO Shibboleth.Application : auto-configuring SSO initiation for protocol (SAML2)
does not appear in the shibd.log
I am pretty sure that it's not relevant, but I'm using the Apache 2.2 Native SP module on 64-bit Linux.
http://svn.shibboleth.net/view/cpp-sp?view=revision&revision=3401
Adding a comment inside of the <SSO> tag in shibboleth2.xml prevents login handlers from being added.
This <SSO> tag does add the appropriate handlers:
<SSO entityID="https://idp.example.com/">
SAML2 SAML1
</SSO>
This <SSO> tag does NOT add the appropriate handlers:
<SSO entityID="https://idp.example.com/">
<
-->
SAML2 SAML1
</SSO>
When the comment is in the configuration file, I get the following error in httpd/native_warn.log when I try to sign in:
2011-02-04 13:42:20 ERROR Shibboleth.Apache [1772] shib_check_user: None of the configured SessionInitiators handled the request.
When the comment is not there, it works as expected.
When shibd is starting up and the comment is present, the SSO auto-configuration is not recorded in the log. That is, a line that looks like:
2011-02-04 13:42:19 INFO Shibboleth.Application : auto-configuring SSO initiation for protocol (SAML2)
does not appear in the shibd.log