AWS + ECP?

[Liam Hoekenga]

On Thu, Feb 4, 2016 at 5:50 PM, Brent Putman <putmanb at georgetown.edu> wrote:

> I suspect you've now got that part working, and you've now got some other
> issues with ECP or authN or profile config that's resulting in the 500 and
> fault, that you need to sort out. So the logs are your friend there..
>

I brought up a v2 IdP and pointed this at it, and get an error that makes
more sense to me..

10:22:43.365 - 35.2.98.216 - DEBUG
[org.opensaml.saml2.binding.AuthnResponseEndpointSelector:99] - Filtering
peer endpoints.  Supported peer endpoint bindings:
[urn:oasis:names:tc:SAML:2.0:bindings:PAOS]
10:22:43.366 - 35.2.98.216 - DEBUG
[org.opensaml.saml2.binding.AuthnResponseEndpointSelector:114] - Removing
endpoint https://signin.aws.amazon.com/saml because its binding
urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST is not supported
10:22:43.366 - 35.2.98.216 - ERROR
[edu.internet2.middleware.shibboleth.idp.profile.AbstractSAMLProfileHandler:447]
- No return endpoint available for relying party urn:amazon:webservices
10:22:43.368 - 35.2.98.216 - DEBUG
[edu.internet2.middleware.shibboleth.idp.profile.saml2.SAML2ECPProfileHandler:278]
- Returning SOAP fault
edu.internet2.middleware.shibboleth.common.profile.ProfileException: No
peer endpoint available to which to send SAML response

I guess I'm not sure how this guy's bash functions would have ever worked.

Liam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160205/ce8c87ae/attachment.html>