Set Up JBoss Server Authentication

We support vulnerability and compliance scans for JBoss servers. Simply create a JBoss Server record with details about your JBoss installation and operating mode. The same record may include details for both Windows and Unix installations.

 

System created authentication records

Did you know? You can allow the system to create JBoss Server authentication records for auto discovered instances and scan them.

Learn how to set this up >>

 

Which technologies are supported?

Windows:

- WildFly version 8.0 and above, JBoss EAP version 6.0 and above

Unix:

- WildFly version 8.0 and above, JBoss EAP version 6.0 and above

 

How do I get started?

- Go to Scans > Authentication.

- Check that you already have a record defined for each host running a JBoss server. For Windows hosts, a Windows record is required. For Unix hosts, a Unix record is required.

- Create a JBoss Server record for the same host (IP). Go to New > Application Records > JBoss Server.

- Before launching a vulnerability scan pick Windows, Unix and JBoss Server authentication in your option profile. (All authentication options are used automatically for compliance scans.)

Tell me about user permissions

 

Windows/Unix Configuration

Choose the Domain Controller operating mode to manage multiple JBoss Application Server instances from a single control point. You'll need to tell us where the Root directory, Base directory and Domain controller are installed.

 

Sample Configurations

 

Windows - Wildfly Standalone mode:

Root Directory - C:\wildfly11

Base Directory - C:\wildfly11\standalone

Base Configuration Directory - C:\wildfly11\standalone\configuration

Configuration File Path - C:\wildfly11\standalone\configuration\standalone.xml

 

Windows - Wildfly Domain Controller mode:

Root Directory - C:\wildfly11

Base Directory - C:\wildfly11\domain

Base Configuration Directory - C:\wildfly11\domain\configuration

Domain Configuration File Path - C:\wildfly11\domain\configuration\domain.xml

Host Configuration File - C:\wildfly11\domain\configuration\host-master.xml

 

Unix - JBoss Standalone mode:

Root Directory - /jboss-eap-6.3

Base Directory - /jboss-eap-6.3

Base Configuration Directory - /jboss-eap-6.3/standalone

Configuration File Path - /jboss-eap-6.3/standalone/configuration/standalone.xml

 

Unix - Wildfly Standalone mode:

Root Directory - /opt/wildfly-11.0.0.Final

Base Directory - /opt/wildfly-11.0.0.Final/standalone

Base Configuration Directory - /opt/wildfly-11.0.0.Final/standalone/configuration

Configuration File Path - /opt/wildfly-11.0.0.Final/standalone/configuration/standalone.xml

 

Unix - Wildfly Domain Controller mode:

Root Directory - /opt/wildfly-11.0.0.Final

Base Directory - /opt/wildfly-11.0.0.Final/domain

Base Configuration Directory - /opt/wildfly-11.0.0.Final/domain/configuration

Domain Configuration File Path - /opt/wildfly-11.0.0.Final/domain/configuration/domain.xml

Host Configuration File - /opt/wildfly-11.0.0.Final/domain/configuration/host-master.xml

 

Unix - Jboss Domain Controller mode:

Root Directory - /jboss-eap-6.3

Base Directory - /jboss-eap-6.3/domain

Base Configuration Directory - /jboss-eap-6.3/domain/configuration

Domain Configuration File Path - /jboss-eap-6.3/domain/configuration/domain.xml

Host Configuration File - /jboss-eap-6.3/domain/configuration/host-master.xml

 

Quick Links

Why use host authentication