Soteria | protecting telemedicine for refugees , using a raspberry pi | Runtime Evironment library

The setup seems somewhat confused. The LoginBacking should not directly call the IdentityStore. Instead, a backing bean should call SecurityContext. The SecurityContext then triggers authentication causing the HttpAuthenticationMechanism to be called, which then, if needed, calls the IdentityStore.

The Soteria project contains a test that demonstrates this for JSF/Faces:

https://github.com/eclipse-ee4j/soteria/tree/master/test/app-mem-customform

The relevant part is:

The WildFly server needs additional configuration:

1. Edit the other Application Security Domain, set the Integrated JASPI property to off.

2. Reload the server

There is also a script for this on: https://github.com/wildfly/quickstart/tree/main/ee-security#configure-the-server

From https://docs.wildfly.org/25/WildFly_Elytron_Security.html#Elytron_and_Java_EE_Security

The EE Security API is built on JASPI. Within JASPI we support two different modes of operation 'integrated', and 'non-integrated'. In integrated mode any identity being established during authentication is expected to exist in the associated security domain. With the EE Security APIs however it is quite likely an alternative store will be in use so configuration the mapping to use 'non-integrated' JASPI allows for identities to be dynamically created as required.

There is a bug in Wildfly versions 13.0.0.Beta1 and 14.0.0.Final when it uses an implementation of HttpAuthenticationMechanism interface with more than one context (ear file with many war's).

Fixed in Wilfly version 15.

Red Hat - BUG Security API - Soteria - Jaspic - Error getting ServerAuthContext

One workaround, it is to separate ear en different instances, one with the context with HttpAuthenticationMecanism and the rest of contexts together.

I'm confused. You've configured the persistence unit to point to a data source managed by your container (java:global/mariadb) and also configured the JDBC properties? You have to make up your mind, either use the datasource provided by the container or configure it yourself, but not both at the same time (in other words, the jta-data-source property is mutually exclusive with the javax.persistence.jdbc.* properties).

You're getting the error because you've set the persistence unit to use JTA, and then you're trying to begin a transaction somewhere using em.getTransaction(), which is not allowed for JTA. Also, you put @PersistenceContext on top of entityManager, which means right after the constructor gets invoked, the entityManager is probably getting overwritten by an injected instance.

The solution is, assuming you do actually want to use JTA, to inject the EntityManager using @PersistenceContext (you shouldn't have to initialize it manually), and then annotating the methods that you want to execute atomically with @Transactional, instead of trying to use entityManager.getTransaction().

I learned that redux-thunk is synchronous, so the event listener is lost by the time the store is updated. So i eventually thought up what is an intuitive react-redux solution by adding itemids param, an array that stores clicked items ids, and updating the UI in RenderBooks() with ternary operators;

I found place where problem exists. Because of some reasone hibernate ingoring my sql server credentials. I fixed this with setting jta-data-source but still i dont know why it not want work with credentials set in persistence.xml.

I had to install the published sources of the win-x64 folder, and not the "publish" folder to make this actually work. This even though my target runtime was win-x64, which would have led me to expect the published result would be in the "publish" folder.

Release folder structure and confusing publish folder