JPA Security: allow pointing to a named persistence unit

[yrodiere]

Description

Currently, JpaIdentityProvider is hardcoded to retrieve the default persistence unit:

quarkus/extensions/security-jpa/runtime/src/main/java/io/quarkus/security/jpa/runtime/JpaIdentityProvider.java

Lines 22 to 27 in 03df5d5

	public abstract class JpaIdentityProvider implements IdentityProvider<UsernamePasswordAuthenticationRequest> {
	private static Logger log = Logger.getLogger(JpaIdentityProvider.class);
	@Inject
	EntityManagerFactory entityManagerFactory;

This means security-related data must live in the default PU and cannot live in a named PU, which seems like a likely scenario.

It would be nice to allow configuring quarkus-security-jpa to use a non-default persistence unit.

See also https://stackoverflow.com/questions/76845856/unsatisfied-dependency-with-panache-and-multiple-datasources

Implementation ideas

AFAICS we just need some more config in the quarkus-security-jpa extension and corresponding build steps to have JpaIdentityProvider retrieve the EntityManagerFactory by name if necessary.

[quarkus-bot]

/cc @sberyozkin (security)

[yrodiere]

Note that #16700 is related, but different, as #16700 is about tenants within a given PU.

[sberyozkin]

Also CC @FroMage @michalvavrik

[FroMage]

Yeah, probably a nice idea.

[michalvavrik]

I've tried to figure how to do this for Hibernate Reactive (JPA Security Reactive), but I don't believe it is possible to use named PU with HR. At least I didn't find any test / any example / any docs and in tests I wrote Mutiny.SessionFactory was not produced for named PU.

#36728 should take care of this for Security JPA.

[yrodiere]

I don't believe it is possible to use named PU with HR

Indeed it is not: https://quarkus.io/guides/hibernate-reactive#hr-limitations ,

#36728 should take care of this for Security JPA.

Thanks!

[michalvavrik]

I don't believe it is possible to use named PU with HR

Indeed it is not: https://quarkus.io/guides/hibernate-reactive#hr-limitations ,

Completely missed that line, thank you.