Fabio Turizo

@jimmc929, apologies for the late reply. I've been testing the SSO behaviour in the latest release of Payara Server Community Edition and it works as advertised: If you login to...

@jimmc929, as I explained in my previous post, the realm configuration is needed to make the SSO feature work, as it was designed using realms rather than the modern Jakarta...

@jimmc929, have you been able to work on the self-contained reproducer that we requested in order to investigate this issue in more detail? Please share it as soon as you...

Greetings @jimmc929, I have been able to reproduce the behaviour you described in the issue by testing the sample application that you shared. Indeed, the first application where the user...

Greetings, @ctabin. After a detailed analysis of your reproducer, we have found that indeed the Payara Embedded API's deployment mechanisms trigger the error that you reported. We have escalated this...

@ctabin, as Steve clarified, the issue's cause is located upstream in the **Gmbal PFL** library, which needs to be patched out first, so at the moment there are no other...

@RedeemerSK, I'm afraid that since this a complex issue that depends on an Oracle database we can't provide assistance without a self-contained reproducer. Can you provide a complete reproducer with...

@RedeemerSK, many thanks for the comprehensive explanation. We agree that the best solution is to fix the underlying issue in Payara Server 5 when using JDK 11 since it guarantees...

@Herr-Sepp, we have an update on your request. Our product manager has proposed a set of enhancements based on your request, and as such the following arguments will be introduced...

@andreasdijkman, I take it by your explanation that if there are port clashes across the 2 instances in your example is due to them running on the same host system,...