Newbie SP problem

[Bryan Wooten]

Ok,

In idp-process.log I see the IDP loading my TrustedPartners-metadata.xml file:
DEBUG [edu.internet2.middleware.shibboleth.common.config.metadata.FilesystemMetadataProviderBeanDefinitionParser:52] - Metadata provider 'TrustedPartners' reading metadata from: /opt/shibboleth-idp/metadata/TrustedPartners-metadata.xml

And:
11:10:03.061 - INFO [edu.internet2.middleware.shibboleth.common.config.relyingparty.RelyingPartyConfigurationBeanDefinitionParser:73] - Parsing configuration for relying party with id: https://idm-3.acs.utah.edu/shibboleth


Now on the SP side if I have in Shibboleth2.xml (using server URL):

<ApplicationDefaults entityID="https://idm-3.acs.utah.edu/shibboleth"
                         REMOTE_USER="eppn persistent-id targeted-id">

I don't get any errors in my app, but I don't get any attributes either.

If I have in Shibboleth2.xml (using my SP metadata entityID):

<ApplicationDefaults entityID="https://sp.attrrelease.utah.edu/shibboleth"
                         REMOTE_USER="eppn persistent-id targeted-id">

I get the "SAML 2 SSO profile is not configured for relying party" from the IDP when I hit the application.

We have a simple PHP app running on the SP's httpd that does display attributes. It has no entry in shibboleth2 nor any metadata.

Sigh, glad its Friday.


Bryan Wooten
Tel: (801)585-9323
Email: bryan.wooten at utah.edu





-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Friday, July 15, 2016 11:29 AM
To: Shib Users <users at shibboleth.net>
Subject: [Ext] RE: Newbie SP problem

> I removed the entry in relying-party.xml and restarted the IDP.
> 
> I still get the same error...

Then you in fact do not have metadata for that SP loaded, so you need to check your assumptions. Even if it weren't reloading the metadata properly, restarting would have picked it up, so...it isn't there.

-- Scott

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