BannerXE, unscoped entityid

Andrew Morgan morgan at orst.edu
Mon Nov 21 19:52:18 EST 2016


On Mon, 21 Nov 2016, Jeffrey Crawford wrote:

> Greetings,
>
> We are trying to get BannerXE to work with SAML. It appears that they don't
> have a concept of using a url like name for the entityID. Because the
> entityID mush match part of the URL for the postback URL
>
> Obviously the AssertionConsumerService can't have another https://
> somewhere in the url. How bad is it to actually have an entityID in our
> local metadata that is not scoped so entityID="service" instead of
> entityID="https://host.domain/sp/service/" There appears to be no way to
> convince the SP that the entityID should look like a url, it has to be a
> short name.
>
> This would not be able to be in the InCommon metadata obviously, but could
> we run into trouble otherwise?

It works fine with a Shibboleth IDP, but it's not compliant with the SAML 
spec.

SAML Metadata spec says the entityID must be a URI.

But, it wouldn't be the first vendor I've dealt with that violated that. 
:(

 	Andy


More information about the users mailing list