Testbed configration: IdPv4 works on Rocky8/JDK 11/Jetty 10/ but not Rocky9/JDK 17/Jetty 11/

[Kevin Buckley]

On 2023/10/06 16:01, Peter Schober via users wrote:
> Kevin Buckley via users <users at shibboleth.net> [2023-10-06 09:16 CEST]:
>> so I thought to go back and re-install IdP 4.3.1 on top of
>> 
>> OS:    Rocky 9
>> JDK:   java-17-openjdk
>> Jetty: 11
>> 
>> so as to have something viable to upgrade from.
> 
> Why not simply copy over /opt/shibboleth-idp from the old machine and
> upgrade that to v5 before ever starting it?
> 
> -peter

Because I got so hung up on the differing requirements, I didn't
actually think of what the upgrade would actually be doing, as
regards ending up with a WAR file to go into the container hosting
application.

Thanks for cutting through the confusion.

On 2023/10/06 20:40, Cantor, Scott wrote:
>>
>> so does that mean that I can't deploy a v4 IdP on top of Jetty 11
>> even though I need to be on Jetty 11 to be able to upgrade the IdP
>> from v4 to v5 ?
> 
> You don't have to be "on" Jetty 11 to upgrade the IdP, it can't be
> upgraded while it's running anyway. It's not on anything at that
> point, it's files on a disk.
> 
> Jetty 11 supports essentially the same configuration as Jetty 10
> other than the logback jars, it’s a lateral update that has to be
> applied at the same time before trying to run it.
> 
> In theory you can also go to Jetty 12 and run either IdP version
> on it.
> 
> In the end: blame Java. Nobody asked for this pointless javax->jakarta
> transition and they all should get tossed into the sun.


Thanks also for same "cut through", and the extra info, although, as
regards Jetty 12, the official docs still say

    "Jetty 12 is very new and likely will need some time for testing and
     to mature, but is supported."

which is why I chose 11.

Anyroad, thanks both.