The management interfaces in Wildfly are secured by default to prevent security violation from remote systems. Local non-HTTP access is protected by a SASL mechanism which consists of a negotiation between the client and the server when the client connects for the first time from the localhost. To access the Wildfly administration console, you must register an Administrator user as follows:

Open a command prompt in the <JBOSS_HOME>/bin directory. Enter ./add-user[.sh|.bat] <username> <password> <ManagementRealm>

After configuring Wildfly administrator user restart the application server. Verify by logon to Wildfly management Console with admin user.

http://(IP Address):9990

System will redirect user to the Wildfly admin console on successful logon.

To use ONEWEB on a new instance of Wildfly 10.0.0.Final, you must establish your database, deploy the provided archives for this server, and perform a number of configuration tasks. You can use one of two operating modes: stand-alone server or managed domain. As a stand-alone server, the operating mode is similar to the previous versions of Wildfly.

ONEWEB requires a full profile. A sample full profile is provided for both stand-alone and domain modes.

The Wildfly Management Console and Management CLI interfaces allow administrators to manage application deployments in a production environment.

To configure ONEWEB on Wildfly you must follow a series of steps:

The first step concerns your choice of persistence and permissions on the database. Create a database for ONEWEB before the deployment of the WAR file. You should create the database schema using the SQL scripts following the details in Prepare Database Server

Connection to the ONEWEB database, as shown in the data source credentials and any subsequent requests to the database are handled through a database user. This database user is for example erp_oneweb.

If you use data source persistence, you must install a driver before creating the data source. Use the below details to install database driver.

Download the JDBC driver from your database vendor. (ex. postgresql.jar)

Add the driver to Wildfly, using Wildfly Management console.

• Click on " Deployments" -> " Add" and select "postgresql.jar", click "Next"

• Check ✔ on Enable and Click "Finish"

The database driver is installed successfully.

The following table gives the datasource connection details for the ONEWEB database.

You can configure the data source by using the JBoss Management Console or the Management CLI. Here, you use the Management Console.

Log in to the JBoss Management Console. By default, http://(IP Address):9990 Navigate to the Datasources panel. Configuration -> Subsystems -> Datasources Select Type "Non-XA" -> and then click add (5) Create datasource -> Choose datasource "custom" and then click "Next"(7)

Specify the details for the new data source. Datasource Attribute Name: Datasource Name JNDI Name: Specifies the JNDI name for the datasource

JDBC Driver Select Detected Driver "postgresql.jar" and then click "Next"

Verify the datasource connection, click "Test Connection" and then click "Finish"

Refer to section for the detailed step by step information on how to deploy ONEWEB.

The org.apache.catalina org.apache.catalina.connector property was used to set UTF-8 encoding in the Wildfly 10 configuration. These properties have no impact since Wildfly now uses Undertow. In order to set UTF-8 encoding instead of changing:

<system-properties>
<property name="org.apache.catalina.connector.URI_ENCODING" value="UTF-8" />
<property name="org.apache.catalina.connector.USE_BODY_ENCODING_FOR_QUERY_STRING" value="true" />
</system-properties>

Editing the standalone.xml as follows

/{WILDFLY_HOME}/standalone/configuration/standalone.xml

Add: system-properties tag

Edit: servlet-container

<servlet-container name="default">

This document will guide on how to enable single sign-on to access different applications deployed into different servers, where these applications belong to the same security domain.

Before you begin You need to have configured security domain which handles authentication and authorization. Verify the application EAR, WAR have use same security-domain

To enable SSO Turn on SSO in Wildfly server configuration Edit the standalone.xml as follows

/{WILDFLY_HOME}/standalone/configuration/standalone.xml.

Edit the standalone.xml as follows

/{WILDFLY_HOME}/standalone/configuration/standalone.xml

Before you configure you should have informed LDAP for configuration authentication with Wildfly Refer to section LDAP Integration

Example:

Add: <login-module> tag

Edit: value ldap setting

Before you Begin To integrate ONEWEB application with the Wildfly authentication, you must register an Application user. Refer to section Step2: Configure access to Wildfly Management Console. You should select type to add user for Application user (b)

Authentication with Wildfly - Edit the standalone.xml as follows

/{WILDFLY_HOME}/standalone/configuration/standalone.xml

Add: <login-module> tag