Chapter 2. Enable Basic authentication


Enable Basic authentication to require a username and password before users can access your Quarkus application. For more information, see Basic authentication.

2.1. Prerequisites

2.2. Procedure

  1. In the application.properties file, set the quarkus.http.auth.basic property to true.

    quarkus.http.auth.basic=true

     

  2. Configure an identity provider to verify the username and password against your user store. For a production application, configure one of the identity provider extensions listed in the Prerequisites, for example, by storing users in a database with the Jakarta Persistence extension. For more information, see the Identity providers guide.
  3. For testing only: In a non-production environment, you can use the embedded realm provided by the quarkus-elytron-security-properties-file extension instead of a production identity provider.

    1. To enable authentication for the embedded realm, set the quarkus.security.users.embedded.enabled property to true.

      quarkus.security.users.embedded.enabled=true

       

    2. You can also configure the required user credentials: user name, password, and roles. For example:

      quarkus.http.auth.basic=true
      quarkus.security.users.embedded.enabled=true
      quarkus.security.users.embedded.plain-text=true
      quarkus.security.users.embedded.users.alice=alice
      quarkus.security.users.embedded.users.bob=bob
      quarkus.security.users.embedded.roles.alice=admin
      quarkus.security.users.embedded.roles.bob=user

      where:

      • The user, alice, has alice as their password and admin as their role.
      • The user, bob, has bob as their password and user as their role.

2.3. Verification

  1. Start your application.
  2. Send a request to a secured endpoint without credentials and confirm that the application returns a 401 Unauthorized response:

    $ curl -i -X GET http://localhost:8080/<your_secured_endpoint>
    
    HTTP/1.1 401 Unauthorized
    WWW-Authenticate: Basic

     

  3. Send the same request with a valid username and password and confirm that the application returns a 200 OK response:

    $ curl -i -X GET -u <username>:<password> http://localhost:8080/<your_secured_endpoint>
    
    HTTP/1.1 200 OK

     

2.4. Next steps

For a more detailed walk-through that shows you how to configure Basic authentication together with Jakarta Persistence for storing user credentials in a database, see the Getting started with Security by using Basic authentication and Jakarta Persistence guide.

2.5. References

Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat Documentation

Legal Notice

Theme

© 2026 Red Hat
Back to top