Polish contribution
Closes gh-5074
This commit is contained in:
@@ -996,7 +996,7 @@ content into your application; rather pick only the properties that you need.
|
||||
management.context-path= # Management endpoint context-path. For instance `/actuator`
|
||||
management.port= # Management endpoint HTTP port. Use the same port as the application by default.
|
||||
management.security.enabled=true # Enable security.
|
||||
management.security.role=ADMIN # Roles required to access the management endpoint.
|
||||
management.security.roles=ADMIN # Comma-separated list of roles that can access the management endpoint.
|
||||
management.security.sessions=stateless # Session creating policy to use (always, never, if_required, stateless).
|
||||
|
||||
# HEALTH INDICATORS (previously health.*)
|
||||
|
||||
@@ -520,14 +520,14 @@ TIP: Generated passwords are logged as the application starts. Search for '`Usin
|
||||
security password`'.
|
||||
|
||||
You can use Spring properties to change the username and password and to change the
|
||||
security roles required to access the endpoints. For example, you might set the following
|
||||
security role(s) required to access the endpoints. For example, you might set the following
|
||||
in your `application.properties`:
|
||||
|
||||
[source,properties,indent=0]
|
||||
----
|
||||
security.user.name=admin
|
||||
security.user.password=secret
|
||||
management.security.role=SUPERUSER
|
||||
management.security.roles=SUPERUSER
|
||||
----
|
||||
|
||||
TIP: If you don't use Spring Security and your HTTP endpoints are exposed publicly,
|
||||
|
||||
Reference in New Issue
Block a user