idp v3.3.3 build with different war file name

[Klingenstein, Nate]

Ah, thanks for explaining.

The IdP's metadata file as generated during install is based on best practices and best guesses at install time only.  It is not modified dynamically in response to any configuration changes or in response to changes in the hosting environment.

You will need to manually edit the metadata for the IdP, and that's something you should be considering doing anyway as a matter of being a good federated identity partner.

--
Dewpoint Identity
https://dewpoint.id
________________________________
From: users <users-bounces at shibboleth.net> on behalf of Pablo Vidaurri <psvidaurri at gmail.com>
Sent: Thursday, July 12, 2018 8:26:59 PM
To: users at shibboleth.net
Subject: Re: idp v3.3.3 build with different war file name

Thanks for the response. We are using tomcat 8, in our case the war file name is being exposed as the webapp context. My main problem is that my endpoints are auto configured with /idp/ in the path. I want to avoid manually editing my idp-metadata to accommodate my intended path of /idp-custom-svc/ because it will be something I would have to remember to adjust for each build.

I assumed since idp.war was being created, then /idp/ was being used in my idp-metdata SSO endpoints.

On Thu, Jul 12, 2018 at 10:22 PM Nate Klingenstein <ndk at dewpoint.id<mailto:ndk at dewpoint.id>> wrote:
Pablo,

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.

https://wiki.shibboleth.net/confluence/display/IDP30/Jetty93

Hope this helps,
Nate.

-----Original message-----
> From: Pablo Vidaurri
> Sent: Thursday, July 12 2018, 8:07 pm
> To: users at shibboleth.net<mailto: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<mailto:users-unsubscribe at shibboleth.net>
>
>
--
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<mailto:users-unsubscribe at shibboleth.net>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20180713/3f1d7f4b/attachment.html>