2.2. Procedure

In the application.properties file, set the quarkus.http.auth.basic property to true.
```
quarkus.http.auth.basic=true
```
Optional: In a non-production environment only and purely for testing Quarkus Security in your applications:
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, secret, 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
  1
  quarkus.security.users.embedded.users.bob=bob
  2
  quarkus.security.users.embedded.roles.alice=admin
  3
  quarkus.security.users.embedded.roles.bob=user
  4
  1 3
  The user, alice, has alice as their password and admin as their role.
  2 4
  The user, bob, has bob as their password and user as their role.
  For information about other methods that you can use to configure the required user credentials, see the Configuring User Information section of the Quarkus "Security Testing" guide.
  중요
  Configuring user names, secrets, and roles in the application.properties file is appropriate only for testing scenarios. For securing a production application, it is crucial to use a database to store this information.