<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>Peter<br><br>Thanks for your input - I can see your point about doing something outside of SP with a script. I think I will experiment with that.<br><span><br><span name="x"></span><div style="text-align: left;"><font size="2"><span style="font-family: verdana,helvetica,sans-serif;"></span></font>Regards<br></div><br>Simon Bright<br>Technical Services Manager<br>E2BN<br>01462 834588<br>07912 853 107<br><a href="http://www.e2bn.org">www.e2bn.org</a><br><br><br><span name="x"></span><br></span><br><hr id="zwchr">* Simon Bright <simon.bright@e2bn.org> [2012-04-25 17:51]:<br>> We are currently configuring our web page(s) with logo'd IDP buttons<br>> for different providers and these buttons are coded with session<br>> initiiator urls see example below. <br>> <br>> https://passport.e2bn.org/Shibboleth.sso/Login?entityID=https://shibboleth-idp.webbased.co.uk/idp/shibboleth&target=https://passport.e2bn.org/secure .... etc <br>> <br>> These work fine but are not very user friendly if we want to tell<br>> other users how to build a button to get to our content from their<br>> own portal/web pages via SSO. <br>> <br>> What I'd like to do is make the coding for the urls more elegant for example <br>> <br>> https://passport.e2bn.org/secure/target/?idp=friendlyIdpname <br>> <br>> I'd like to use the Request Mapper to take this url and route the<br>> request to the appropriate idp entity ID based on the<br>> friendlyIdpname part , either directly or via a named dedicated<br>> session initiator within the shibboleth2.xml file <br><br>Why not simply point those sites to a script of your own (outside the<br>Shib SP and outside a protected directory), where you can make up<br>request parameters and parse them and generate redirects to your<br>hearts content? I don't see the advantage letting the SP do this.<br><br>If you don't insist on generating what is referred to as NASCAR-style<br>IdP discovery you might want to look at the Shibboleth EDS or maybe<br>discojuice.org, both of which are modern discovery interfaces designed<br>with improved user experience and functional elegance in mind.<br><br>> Can I somehow use the Query Name function within the request mapper<br>> to do this , by linking a requireSessionWith (sessioninitiator) or<br>> by otherwise declaring the idp entity id to use.<br>> <br>> The Request Mapper documentation seems to suggest this but I cannot<br>> find any examples.<br>> <br>> Can you help by commenting if this is posible and if so how the<br>> Query Name part should be located and configured within the Request<br>> Mapper e.g does it go in the Access Control Part or outside it.<br><br>I obviously don't understand what you're up to, so bear with me:<br>Why is the request mapper and the way you require sessions relevant<br>here? If you hand out custom URLs that get rewritten to session<br>initiator requests there's no ShibRequireSession involved, no?<br>-peter<br>--<br>To unsubscribe from this list send an email to users-unsubscribe@shibboleth.net<br></div></body></html>