[External]Re: Trouble running Shibboleth with Jetty

[Paul B. Henson]

On 8/28/2025 12:18 PM, Reginald Dancy wrote:

> So I enabled the EE9 module

? That does not appear to be what occurred based on your transcript? It 
appears you just re-enabled the already enabled EE10 module?

> [1006]root at metdv-shibidp9:/opt/jetty-base # java -jar /opt/jetty/ 
> start.jar --add-modules=ee10-deploy
> 
> INFO  : ee10-deploy already enabled by [${jetty.base}/start.d/ee10- 
> deploy.ini]

And then modified the idp deployment to use EE10 instead of EE9?

> Afterwards, I edited the idp.xml file and changed EE9 to EE10. Then I 
> ran the start.jar file and it loaded shibboleth with no errors.

I don't recall if the idp works okay with EE10, but the current 
recommended jetty configuration:

https://shibboleth.atlassian.net/wiki/spaces/IDP5/pages/3516104706/Jetty12

specifies EE9.

> (http://localhost/idp/status <http://localhost/idp/status>) Connection 
> refused

As Scott pointed out, perhaps you don't have jetty configured to listen 
on port 80. I generally configure the idp to only accept port 443 from 
the Internet, but allow port 80 from localhost for management purposes.

Beyond that, if jetty successfully starts the idp webapp but it's not 
working right, you should take a look at the idp log files and see what 
they have to say.