-
Notifications
You must be signed in to change notification settings - Fork 88
guide authentication quarkus
Warning
|
Hey there! Seems like you are still using the documentation of our legacy Java repository. Since it won’t be maintained anymore, we recommend you to checkout the new Java page here. |
Quarkus supports different authentication mechanisms through different extensions. For example:
-
quarkus-elytron-security-properties-file
provides support for simple properties files that can be used for testing security. This supports both embedding user information inapplication.properties
and standalone properties files. -
quarkus-security-jpa
provides support for authenticating via JPA. -
quarkus-elytron-security-jdbc
provides support for authenticating with JDBC -
quarkus-smallrye-jwt
provides support for authenticating using JSON Web Tokens. It allows you to inject the token and claims into the application as per the MicroProfile JWT specification. -
quarkus-oidc
provides support for authentication via an OpenID Connect provider e.g. KeyCloak -
quarkus-keycloak-authorization
provides support for a policy enforcer using Keycloak Authorization Services.
For mix authentication, see here.
For further details see Quarkus - Security architecture and guides. Quarkus also provides a compatibility layer for Spring Security in the form of the spring-security
extension.
This documentation is licensed under the Creative Commons License (Attribution-NoDerivatives 4.0 International).