Cansecurity-jpa support more than one IdentityProvider ?

Cansecurity-jpa support more than one IdentityProvider ?

Yes. Form-based authentication requires other provider. You can check out my tests, thehttpSecurity.mechanism(form, jpa) wouldn't work.

What is not clear to me is why these identity providers and augmentors must be used instead of CDI registered identity providers and augmentors, while the mechanism is not meant to be used instead of other mechanisms.

Before I answer, I would like to summarize so that we speak about the same thing:

• this method adds a new mechanism (likenew CustomAuthMechanism or any other mechanism at all) and allows you to use your own identity providers and augmentors
• if you want to use global identity providers or augmentors, then don't use it
• if you want to use global identity providers/augmentors and some other providers/augmentors, specific for only this mechanism, you can create collection with global identity providers/augmentors and your own, specific for only this mechanism; nothing stops you

What is not clear to me is why these identity providers and augmentors must be used instead of CDI registered identity providers and augmentors, while the mechanism is not meant to be used instead of other mechanisms.

• how many times do you want to use both identity providers registered as CDI beans and dedicated ones for this mechanism? I'd say you usually need one or two
• this methods facilitates programmatic setup for Quarkus Security JPA, if withhttpSecurity.basic() we already use Quarkus Security JPA from CDI, then why would we need the programmatic setup at all? Only answer I could come with is flexibility - unlike CDI providers, which are there for every mechanism, here you can explicitly select which provider and augmentors you want to apply