annotation. It provides hints for people reading the code, and for Spring, that the class plays a specific role. In this case, our class is a web @Controller so Spring will consider it when handling incoming web into AuditEvents and published to the AuditService. The default user will have the ADMIN role as well as the USER role. The Actuator security features can be modified using external properties (management security role required to access the endpoints. For example, you might set the following in your application.properties: security.user.name=admin security.user.password=secret management.security.role=SUPERUSER

annotation. It provides hints for people reading the code, and for Spring, that the class plays a specific role. In this case, our class is a web @Controller so Spring will consider it when handling incoming web into AuditEvents and published to the AuditService. The default user will have the ADMIN role as well as the USER role. The Actuator security features can be modified using external properties (management security role required to access the endpoints. For example, you might set the following in your application.properties: security.user.name=admin security.user.password=secret management.security.role=SUPERUSER

annotation. It provides hints for people reading the code, and for Spring, that the class plays a specific role. In this case, our class is a web @Controller so Spring will consider it when handling incoming web into AuditEvents and published to the AuditService. The default user will have the ADMIN role as well as the USER role. The Actuator security features can be modified using external properties (management security role required to access the endpoints. For example, you might set the following in your application.properties: security.user.name=admin security.user.password=secret management.security.role=SUPERUSER

annotation. It provides hints for people reading the code, and for Spring, that the class plays a specific role. In this case, our class is a web @Controller so Spring will consider it when handling incoming web into AuditEvents and published to the AuditService. The default user will have the ADMIN role as well as the USER role. The Actuator security features can be modified using external properties (management security role required to access the endpoints. For example, you might set the following in your application.properties: security.user.name=admin security.user.password=secret management.security.role=SUPERUSER

annotation. It provides hints for people reading the code, and for Spring, that the class plays a specific role. In this case, our class is a web @Controller so Spring will consider it when handling incoming web into AuditEvents and published to the AuditService. The default user will have the ADMIN role as well as the USER role. The Actuator security features can be modified using external properties (management security role required to access the endpoints. For example, you might set the following in your application.properties: security.user.name=admin security.user.password=secret management.security.role=SUPERUSER

annotation. It provides hints for people reading the code, and for Spring, that the class plays a specific role. In this case, our class is a web @Controller so Spring will consider it when handling incoming web into AuditEvents and published to the AuditService. The default user will have the ADMIN role as well as the USER role. The Actuator security features can be modified using external properties (management security role required to access the endpoints. For example, you might set the following in your application.properties: security.user.name=admin security.user.password=secret management.security.role=SUPERUSER

annotation. It provides hints for people reading the code, and for Spring, that the class plays a specific role. In this case, our class is a web @Controller so Spring will consider it when handling incoming web AuditEvents and published to the AuditService. • The default user will have the ADMIN role as well as the USER role. The Actuator security features can be modified using external properties (management security role required to access the endpoints. For example, you might set the following in your application.properties: security.user.name=admin security.user.password=secret management.security.role=SUPERUSER

annotation. It provides hints for people reading the code, and for Spring, that the class plays a specific role. In this case, our class is a web @Controller so Spring will consider it when handling incoming web AuditEvents and published to the AuditService. • The default user will have the ADMIN role as well as the USER role. The Actuator security features can be modified using external properties (management security role required to access the endpoints. For example, you might set the following in your application.properties: security.user.name=admin security.user.password=secret management.security.role=SUPERUSER

annotation. It provides hints for people reading the code, and for Spring, that the class plays a specific role. In this case, our class is a web @Controller so Spring will consider it when handling incoming web AuditEvents and published to the AuditService. • The default user will have the ADMIN role as well as the USER role. The Actuator security features can be modified using external properties (management security role required to access the endpoints. For example, you might set the following in your application.properties: security.user.name=admin security.user.password=secret management.security.role=SUPERUSER

annotation. It provides hints for people reading the code, and for Spring, that the class plays a specific role. In this case, our class is a web @Controller so Spring will consider it when handling incoming web AuditEvents and published to the AuditService. • The default user will have the ADMIN role as well as the USER role. The Actuator security features can be modified using external properties (management security role required to access the endpoints. For example, you might set the following in your application.properties: security.user.name=admin security.user.password=secret management.security.role=SUPERUSER