Add a JPA Identity Extension

[stuartwdouglas]

This extension would allow for an easy annotation driven approach to creating JPA entities that represent a user. An entity can be annotated with @Username and @password (and maybe @salt) to inform Quarkus that this entity represents a user. Quarkus will then automatically wire up authentication based on this entity.

[FroMage]

Looking at it for prototyping.

[FroMage]

Well, I stopped looking at it, but I do have a branch with the start of this. I hit the issue that it appears that the credentials are being looked up outside of a scope in which ArC can deliver an EntityManager (so probably outside the request scope), which I'm not sure how to fix. I can probably get an EntityManagerFactory and create one, but it's probably not right performance-wise?

[stuartwdouglas]

We need to create the request scope earlier then I guess. I was trying to avoid this as there is some complexity in dealing with this if the thread is propagated between different threads.

Creating an EntityManager is also a solution (and should not really be a perf issue, they are supposed to be fairly cheap), but it means that if we are going to stick the user entity into the SecurityIdentity then it will be a detached entity, although this might be ok.

[Sanne]

yes EntityManager instances are fairly cheap now. Feel free to ping me when this is done, happy to review the ORM usage to be kinda "lean".

+1 to detach entities as long as there's no uninitialized paths in the loaded graph - I assume it's going to be a simple, relationless entity?

[FroMage]

It's almost done here: #5660