Hello ,
We've been trying to configure SSO with NAM as IDP and another aplication using Tomcat+Shibboleth as SP.
After we see initial log screen and we try to log we see the following message in catalina.out:
<amLogEntry> 2016-08-04T13:09:25Z WARNING NIDS SAML2: Entity Provider not found with the provider id as https://embr-dev.ptcmanaged.com/WebUI/ </amLogEntry>
Warning: Invalid resource key: Request was from an untrusted provider. No prefix!
I am not a NAM specialist, but we've already checked in NAM and the entity ID is set as a trusted provider.
I suspect NAM is not being able to identify the SP when the AuthnRequest comes.
Here's the authentication request that is being sent from SP->IdP
<samlp:AuthnRequest xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" AssertionConsumerServiceURL="https://embr-dev.ptcmanaged.com/Shibboleth.sso/SAML2/POST" Destination="https://idsqas.embraer.com.br/nidp/saml2/sso" ID="_3f6ac8806d0c603d4e66e6bac7b163e8" IssueInstant="2016-08-04T13:36:42Z" ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindi ngs:HTTP-POST" Version="2.0"><saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" >https://embr-dev.ptcmanaged.com/WebUI/</saml:Issuer><samlp:NameIDPolicy AllowCreate="1"/></samlp:AuthnRequest>
I wonder if the issuer element is not matching with NAM and then NAM refuses the request because does not know the issuer?
Can you please confirm where this Issuer element should be entered in NAM side?
Thanks
We've been trying to configure SSO with NAM as IDP and another aplication using Tomcat+Shibboleth as SP.
After we see initial log screen and we try to log we see the following message in catalina.out:
<amLogEntry> 2016-08-04T13:09:25Z WARNING NIDS SAML2: Entity Provider not found with the provider id as https://embr-dev.ptcmanaged.com/WebUI/ </amLogEntry>
Warning: Invalid resource key: Request was from an untrusted provider. No prefix!
I am not a NAM specialist, but we've already checked in NAM and the entity ID is set as a trusted provider.
I suspect NAM is not being able to identify the SP when the AuthnRequest comes.
Here's the authentication request that is being sent from SP->IdP
<samlp:AuthnRequest xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" AssertionConsumerServiceURL="https://embr-dev.ptcmanaged.com/Shibboleth.sso/SAML2/POST" Destination="https://idsqas.embraer.com.br/nidp/saml2/sso" ID="_3f6ac8806d0c603d4e66e6bac7b163e8" IssueInstant="2016-08-04T13:36:42Z" ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindi ngs:HTTP-POST" Version="2.0"><saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" >https://embr-dev.ptcmanaged.com/WebUI/</saml:Issuer><samlp:NameIDPolicy AllowCreate="1"/></samlp:AuthnRequest>
I wonder if the issuer element is not matching with NAM and then NAM refuses the request because does not know the issuer?
Can you please confirm where this Issuer element should be entered in NAM side?
Thanks