Red Hat Training

A Red Hat training course is available for Red Hat Fuse

Chapter 4. Accessing the Fuse Console for Karaf

To access the Fuse Console for Apache Karaf standalone:

  1. Install Fuse on the Karaf container. For step-by-step instructions, see Installing on Apache Karaf.

  2. In the command line, navigate to the directory in which you installed Red Hat Fuse and run the following command to start Fuse standalone: 

    ./bin/fuse

    The Karaf console starts and shows version information, the default Fuse Console URL, and a list of common commands.

  3. In a browser, enter the URL to connect to the Fuse Console. For example: http://localhost:8181/hawtio
  4. In the login page, enter your user name and password and then click Log In.

By default, the Fuse Console shows the Home page. The left navigation tabs indicate the running plugins.

4.1. Securing Fuse containers on Karaf

You can implement the following security features to secure Fuse containers on Apache Karaf:

  • Enable SSL/TLS security
  • Configure user authorization

4.1.1. Enabling SSL/TLS security

SSL/TLS security is not enabled by default for the Fuse Console. It is recommended that you enable SSL/TLS security on the Fuse Console to protect username/password credentials from snooping. For detailed instructions on how to enable SSL/TLS security, see the Security Guide.

4.1.2. Controlling user access to the Fuse Console

Note

For this release, role-based access control for the Fuse Console is only enabled for Fuse on Karaf standalone.

The operations that an authenticated user are allowed to perform depend on the role (or roles) assigned to that user, as listed in Table 4.1, “Role-based access on Karaf standalone”.

Ensure that you have the necessary user role authorization to perform the Fuse Console operations that you want to perform.

To set a user role:

  1. Open the Red Hat Fuse etc/users.properties file in an editor.

  2. Add an entry for the user name, password, and role.

    For example, the following entry in the etc/users.properties file defines the admin user and grants the admin role. 

    admin = secretpass,admin
  3. Save the file.

Table 4.1. Role-based access on Karaf standalone

Operationadminmanagerviewer

login/logout

Y

Y

Y

View Help topics

Y

Y

Y

Set user preferences

Y

Y

Y

Connect

   

Discover and connect to remote integrations

Y

Y

Y

Discover and connect to local integrations

Y

Y

Y

Camel

   

View all running Camel applications

Y

Y

Y

Start, suspend, resume, and delete Camel Contexts

Y

Y

N

Send messages

Y

Y

N

Add endpoints

Y

Y

N

View routes, route diagrams, and runtime statistics

Y

Y

Y

Start and stop routes

Y

Y

N

Delete routes

Y

Y

N

JMX

   

Change attribute values

Y

Y

N

Select and view attributes in a time-based chart

Y

Y

Y

View operations

Y

Y

Y

OSGI

   

View bundles, features, packages, services, servers, framework, and configurations

Y

Y

Y

Add and delete bundles

Y

Y

N

Add configurations

Y

Y

N

Install and uninstall features

Y

Y

N

Runtime

   

View system properties, metrics, and threads

Y

Y

Y

Logs

   

Viewing logs

Y

Y

Y

For more information on role-based access control, see Deploying into Apache Karaf.