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 considers it when handling incoming web OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. */ package org.springframework.boot.docs.springbootfeatures OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. */ package org.springframework.boot.docs.springbootfeatures

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 auth. The following properties can be used to customize the security configuration: security.user.role security.basic.authorize-mode security.basic.enabled Chapter 30. Using jOOQ Java Object Oriented

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 auth. The following properties can be used to customize the security configuration: security.user.role security.basic.authorize-mode security.basic.enabled Chapter 30. Using jOOQ Java Object Oriented

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 auth. The following properties can be used to customize the security configuration: security.user.role security.basic.authorize-mode security.basic.enabled Chapter 30. Using jOOQ Java Object Oriented

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 auth. The following properties can be used to customize the security configuration: security.user.role security.basic.authorize-mode security.basic.enabled Chapter 30. Using jOOQ Java Object Oriented

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 auth. The following properties can be used to customize the security configuration: security.user.role security.basic.authorize-mode security.basic.enabled Chapter 30. Using jOOQ Java Object Oriented

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 auth. The following properties can be used to customize the security configuration: • security.user.role • security.basic.authorize-mode • security.basic.enabled Spring Boot Reference Guide 1.3.7.RELEASE

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 auth. The following properties can be used to customize the security configuration: • security.user.role • security.basic.authorize-mode • security.basic.enabled Spring Boot Reference Guide 1.3.9.BUILD-SNAPSHOT

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 auth. The following properties can be used to customize the security configuration: • security.user.role • security.basic.authorize-mode • security.basic.enabled Spring Boot Reference Guide 1.4.0.M2

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 auth. The following properties can be used to customize the security configuration: security.user.role security.basic.authorize-mode security.basic.enabled Chapter 30. Using jOOQ Java Object Oriented