OpenAthens SP to Shibboleth (using OA Federation): Deep Links

[Manoj Kancharla]

2016-01-28 11:13:32 ERROR OpenSAML.MessageDecoder.SAML2POST [1]: POST targeted at (https://jama.amadev.silverchair.com/Shibboleth.sso/SAML2/POST), but delivered to (https://amadev.silverchair.com/Shibboleth.sso/SAML2/POST) 
2016-01-28 11:14:35 ERROR OpenSAML.MessageDecoder.SAML2POST [1]: POST targeted at (https://jama.amadev.silverchair.com/Shibboleth.sso/SAML2/POST), but delivered to (https://amadev.silverchair.com/Shibboleth.sso/SAML2/POST)

SAML Request
<samlp:AuthnRequest xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"
                    AssertionConsumerServiceURL="https://jama.amadev.silverchair.com/Shibboleth.sso/SAML2/POST"
                    Destination="https://auth.athensams.net/oahf"
                    ID="_8eb9f859f9c87fc13f08bba2d8db468f"
                    IssueInstant="2016-01-28T16:14:27Z"
                    ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
                    Version="2.0"
                    >
    <saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">https://sp.silverchair.com/ama/development/shibboleth</saml:Issuer>
    <samlp:NameIDPolicy AllowCreate="1" />
</samlp:AuthnRequest>


-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Thursday, January 28, 2016 11:32 AM
To: Shib Users
Subject: RE: OpenAthens SP to Shibboleth (using OA Federation): Deep Links

> In Shibboleth2.xml, I added an additional <Host> entry for the 
> subdomain site and added an <Alias> within <Site> for the subdomain 
> host. That didn't help. I'm stuck!

Aliases in that spot are used to allow for requests with different hostnames in them into the same vhost. I have no idea if what's what you're trying to do or not.

I told you to use the logs. Until you do that, you're just blind to what it's actually doing. The error message in shibd.log would also clearly identify what URL it *thinks* got requested that didn't match the message, and you haven't provided that either.

The native.log, on DEBUG, will log every request it sees and what URL it got mapped into. And that's pretty much 99% of diagnosing this.

-- Scott

--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net