Set Up IBM WebSphere App Server Authentication

Create an IBM WebSphere App Server record in order to authenticate to a WebSphere Application Server running on a Unix host or Windows host, and scan it for compliance. The same record may include details for both Windows and Unix installations. You'll also need a Unix record for the unix host running the web server and a Windows records for the Windows host running the web server.

This record type is only available in accounts with PA or SCA and is only supported for compliance scans.

System created authentication records

Did you know? You can allow the system to create IBM WebSphere App Server authentication records for auto discovered instances and scan them. You can choose to have instances discovered at the installation directory level or the server directory level.

Learn how to set this up >>

Which technologies are supported?

For the most current list of supported authentication technologies and the versions that have been certified for VM and PA by record type, please refer to the following article: 

Authentication Technologies Matrix

How do I get started?

- Go to Scans > Authentication.

- Check that you already have a record defined for each host running a IBM WebSphere App Server. For Windows hosts, a Windows record is required. For Unix hosts, a Unix record is required.

- Create an IBM WebSphere App Server record for the same host. Go to New > Applications > IBM WebSphere App Server.

Note: If the Network Support feature is enabled, then the Windows/Unix record must have the same network selected as the IBM WebSphere App Server record.

Tell me about user permissionsTell me about user permissions

Windows Installation / Unix Installation

On the Windows Installation tab, enter the installation directory where your application server is installed.

On the Unix Installation tab, you'll enter the installation or server directory path and choose the IBM WAS discovery mode. Do one of the following:

- enter the installation directory path (e.g. /opt/IBM/WebSphere/AppServer) and select "IBM WAS Installation Directory"

- enter the server directory path (e.g. /opt/IBM/WebSphere/AppServer/profiles/AppSrv02/config/servers/server1) and select "IBM WAS Server Directory"

How does it work?

We'll authenticate to each target host using the credentials provided in the Unix record or Windows Record. If the host is running WebSphere Application Server then we'll check to see if an IBM WebSphere App Server record exists. If yes, we'll use credentials from the Unix record/Windows record to authenticate to the Unix/Windows system, access the application server configuration, and scan it for compliance.

Do you have Tag Support enabled?

If your subscription has Tag Support for Authentication Records enabled, then you'll see additional options for specifying hosts using asset tags. Choose an asset type and then provide IPs or tags to the record. Your asset type options are: IPs/Ranges, IP Range in Tag Rule and Asset Tags.

For domain level authentication, you can only add assets when the domain type is NetBIOS, User-Selected IPs. The Assets section is disabled when the domain type is NetBIOS, Service-Selected IPs, or Active Directory.  

Asset Type: IPs/Ranges
Use this option to add IP addresses/ranges to the record. Enter the IP addresses/ranges in the field provided.

Asset Type: IP Range in Tag Rule
Use this option to add tags that have IP address ranges defined in the tag rule. All IP addresses defined in the tag rule will be associated with the record, including IPs that don’t already have the tag assigned. Click Add Tag to pick tags to include or exclude. Note that only tags with the dynamic tag rule “IP Address in Range(s)” will be available in the tag selector.

Asset Type: Asset Tags
Use this option to add tags to the record for the assets you want included. IP addresses with the selected tags already assigned will be associated with the record. Click Add Tag to pick tags to include or exclude.

Learn more about tag support for authentication records