Fuse 6 is no longer supported
As of February 2025, Red Hat Fuse 6 is no longer supported. If you are using Fuse 6, please upgrade to Red Hat build of Apache Camel.Ce contenu n'est pas disponible dans la langue sélectionnée.
2.4. Configuring Roles for the Administrative Protocols
Overview Copier lienLien copié sur presse-papiers!
Copier lienLien copié sur presse-papiers!
By configuring each of the administrative functions to use a different role for authorization, you can provide fine grained control over who can monitor and manipulate running containers.
Administration protocols Copier lienLien copié sur presse-papiers!
Copier lienLien copié sur presse-papiers!
You can independently configure roles for the following different administrative protocols:
- SSH (remote console login)
- JMX management
Default role Copier lienLien copié sur presse-papiers!
Copier lienLien copié sur presse-papiers!
The default role name for all of the administration protocols is set by the
karaf.admin.role
property in the Red Hat JBoss Fuse's etc/system.properties
file. For example, the default setting of karaf.admin.role
is:
karaf.admin.role=admin
karaf.admin.role=admin
You have the option of overriding the default
admin
role set by karaf.admin.role
for each of the administrative protocols.
Changing the remote console's role Copier lienLien copié sur presse-papiers!
Copier lienLien copié sur presse-papiers!
To override the default role for the remote console add a
sshRole
property to the org.apache.karaf.shell
PID. The following sets the role to admin
:
sshRole=admin
sshRole=admin
Changing the JMX role Copier lienLien copié sur presse-papiers!
Copier lienLien copié sur presse-papiers!
To override the default role for JMX add a
jmxRole
property to the org.apache.karaf.management
PID. The following sets the role to jmx
:
jmxRole=jmx
jmxRole=jmx