URL encoding the entity ID in Velocity

[Nate Klingenstein]

That actually raises an interesting orthogonal question.  I don’t know if the discovery protocol has any means for a relying party to specify selection caching preferences.

http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-idp-discovery.pdf

This is obviously better than nothing, but I could imagine that people who are stuck at the wrong IdP will often be there because they told a discovey service to remember the wrong selection.

> On Feb 3, 2016, at 11:19, Wessel, Keith <kwessel at illinois.edu> wrote:
> 
> Hi,
> 
> We're adding a link to our IDP login page that will point users back to the centralized discovery service should they choose the wrong campus. That'll allow them to clear their selection and try again.
> 
> We could just make this a static page, but we'd ideally like to pass the entityID of the SP back to the discovery service. To do this, I'm thinking we'll ned to URL encode the entityID. Is there an easy way to do this in Velocity witouth changing the IDP source to pass another variable into Velocity to define a java.net.URLEncoder object?
> 
> Or is there another way to encode this?
> 
> Or can I perhaps just grab the URL-encoded entityID from the request object somehow?
> 
> Thanks,
> Keith
> 
> -- 
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net