CAS issue, not RTFM'n enough?

[Marvin Addison]

On Wed, Mar 2, 2016 at 12:28 PM John Morrison <john.morrison at uadm.uu.se>
wrote:

> Where is this 127.0.1.1 coming from and then trying www.apereo.org?


That's simply a profile URI that happens to be an HTTPS URL. No connections
are made to anything at apereo.org. I may need to document that because
it's a point of confusion that has come up before.


> [net.shibboleth.idp.cas.flow.impl.BuildRelyingPartyContextAction:84] -
> Setting up RP context for unverified relying party
> https://127.0.1.1/cas/
> 2016-03-02 18:19:36,050 - DEBUG
> [net.shibboleth.idp.relyingparty.impl.DefaultRelyingPartyConfigurationResolver:293]
> - Resolving relying party configuration
> 2016-03-02 18:19:36,050 - DEBUG
> [net.shibboleth.idp.relyingparty.impl.DefaultRelyingPartyConfigurationResolver:299]
> - Profile request is unverified, returning configuration
> shibboleth.UnverifiedRelyingParty
>

That's the problem. You're testing a CAS client on the loopback address,
and it's not registered in cas-protocol.xml. Because no matching service is
found, it's using the "unverified" relying party configuration which does
not have CAS protocol support configured by default.

M <users-unsubscribe at shibboleth.net>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160302/df3de587/attachment.html>