idp v3.3.3 build with different war file name
ndk at dewpoint.id
Thu Jul 12 23:21:38 EDT 2018
The .war file is just basically a package for the webapp. It doesn't do any actual mapping and the file name is never exposed to the outside world.
If you want to expose a Shibboleth IdP at a different URL, the method for doing that depends on your web server and deployment model. For instance, with Jetty and a deployment descriptor, you would change the contextPath.
Hope this helps,
> From: Pablo Vidaurri
> Sent: Thursday, July 12 2018, 8:07 pm
> To: users at shibboleth.net
> Subject: idp v3.3.3 build with different war file name
> Even though I have defined my entityId during the install as something like https://www.some.company.com/ <https://www.some.company.com/>idp-custom-svc/shibboleth
> my war file is still named as idp.war and all my endpoints (POST, REDIRECT, etc) in my idp-metadata file are still formatted as https://www.some.company.co <http://www.some.company.co>/idp/profile/Shibboleth/SSO
> Is there a way to specify an alternate war file or at least what path to use for my endpoints (use idp-custom-svc instead of idp)?
> For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
More information about the users