open-liberty | Open Liberty | Microservice library

Usings the OpenLiberty sessionCache-1.0 feature with HazelCast enables you to easily persist and share session data in a HazelCast in-memory cluster as explained here: https://openliberty.io/guides/sessions.html.

However in this setup session data is stored internally in the maps named: com.ibm.ws.session.attr.[app-context-root] & com.ibm.ws.session.meta.[app-context-root] as indicated here (I don't see the OpenLiberty docs clearly specifying this though)

This prevents different apps (with different context-roots) to share session data since they are writing and reading session data from different named maps.

Is there a way to overwrite this name to enable apps with different context-roots to read write from the same map to share session data?

I was going over the httpSession- and httpSessionCache-properties in the OpenLiberty docs but could not find any attribute supporting such a thing.

I encountering a problem when sending a GET request from Postman to test my endpoints. The same NamedQueries worked before with Derby with just the one Schema, so no need to differentiate then. I have now changed to DB2 running in a local Docker instance and am using Maven to run Open-Liberty Framework to create the endpoints. I am receiving the below error. Do I need to create a orm.xml file with entity-mappings, or do something else to resolve this? I would prefer to do this without more xml files if possible.

Postman:

Error 500: java.lang.NullPointerException: Cannot invoke >"javax.persistence.EntityManager.createNamedQuery(String, java.lang.Class)" because "this.em" is null

Maven:

[INFO] [ERROR ] CWWJP0015E: An error occurred in the org.eclipse.persistence.jpa.PersistenceProvider persistence provider when it attempted to create the container entity manager factory for the jpa-unit persistence unit. The following error occurred: Exception [EclipseLink-28019] (Eclipse Persistence Services - 2.7.9.v20210604-2c549e2208): org.eclipse.persistence.exceptions.EntityManagerSetupException

[INFO] Exception Description: Deployment of PersistenceUnit [jpa-unit] failed. Close all factories for this PersistenceUnit.
[INFO] Internal Exception: Exception [EclipseLink-0] (Eclipse Persistence Services - 2.7.9.v20210604-2c549e2208): org.eclipse.persistence.exceptions.JPQLException
[INFO] Exception Description: Problem compiling [SELECT u FROM Sankofa.Users u].
[INFO] [14, 29] 'Sankofa.Users u' cannot be the first declaration of the FROM clause.

UserDao

I observe that the element, though it points to a valid Dockerfile is not honored by liberty:devc.

Consider this output from mvn help:effective-pom:

I'm building a Quarkus app which handles http requests with resteasy and calls another api with restclient and I need to propagate a header and add another one on the fly so I added a class that implements ClientHeadersFactory.

Here's the code:

My organization already has some web applications deployed on a liberty server, using its SSO, which sets an LtpaToken cookie for the entire intranet domain.

Now we are switching to openidconnect authenticated, sessionless (with JWT) secured web applications.

Authentication is working fine - only the browser is involved - and authorization is also working fine (with feature mpJwt-1.1).

But when the user comes from another web application (within the same session), the browser sends LtpaToken2 cookie and liberty rejects the request with 401 (unauthorized).

I'd like to:

1. completely ignore whichever LtpaToken cookie happens to come in the request (yes, completely ignore, as if it was never there, either valid or invalid, or expired or whatever, our new applications could never care less for the older SSO scheme);
2. never ever generate an LtpaToken once the first request with a valid JWT token comes in.

EDIT

The 2nd point above is not really happening (to be clear, this new liberty server is not generating an LtpaToken).

I've managed to create a MWE, comprising (in fact so minimal that you only need the server.xml and any index.html):

(server.xml)

I try to run a microservice (based on Eclipse Microprofile) on OpenLiberty (v20.0.0.1/wlp-1.0.36.cl200120200108-0300) on Eclipse OpenJ9 VM, version 1.8.0_242-b08 (en_US))

I run the server as the official Docker image (open-liberty:kernel)

In my service I try to connect to another rest service via HTTPS

Currently we are trying to build a docker image with openliberty 20.0.0.3 with webprofile6 with java 8, we were able to do this with websphere liberty full profile image but not with the full profile image from open-liberty.

Is this something expected?

There is a way to have availble it in open-liberty?

Thanks

Michele

I configured the Open Liberty server inside Eclipse 2020-03 using the Eclipse Developer Tools from https://openliberty.io/downloads/#eclipse_developer_tools.

I can add my .war project and start the server without problem, but publishing on the running server results in an Error:

Also at startup there is an error in the server console:

The OpenLiberty Docker Images tagged as full contain a server.xml that only enables the javaee-8.0 feature. Those tagged as microProfile3 only enable microProfile-3.0.

I want both... even better: I'd like to have just all features enabled while I'm developing; I'll optimize for performance when I need it, i.e. maybe not at all.

Is there an easier way than to build another image with both features enabled?