Setup template on Linux - CustomerID
Ubisecure CustomerID uses the same Ubisecure Directory as Ubisecure SSO. For this reason, Ubisecure CustomerID needs some of the configuration details from the Ubisecure SSO configuration. This chapter describes how this information can be added to the Ubisecure CustomerID configuration. The other properties can be adjusted according to the needs of the specific installation environment.
Create a copy of the Ubisecure CustomerID configuration template:
cd /usr/local/ubisecure/customerid/application cp config/linux.config ./
Copy entries from Ubisecure SSO configuration file to Ubisecure CustomerID configuration file:
Copy some values from Ubisecure SSO
ubilogin-sso/ubilogin/unix.configfile to the Ubisecure CustomerIDcustomerid/application/linux.configfile. The following table shows what key values to copy and where:From: Ubisecure SSO
To: Ubisecure CustomerID
master.secret
master.secret
uas.url
uas.url
ldap.url
ldap.url
suffix
ldap.suffix
NOTE: Check that there are no additional control characters or white space at the end of
uas.url-value. In fact, make this same check for all values as you proceed.The rest of the fields in the Ubisecure CustomerID
linux.configfile can be defined independently from the Ubisecure SSO.
Edit linux.config
Field Name | Field Description |
|---|---|
| ubilogin.home | This is the path to the location where Ubisecure SSO has been installed. |
| eidm.url | This is the publicly visible URL address of your Ubisecure CustomerID installation. The value must not include a path component and must not end with a '/' character. This address must be accessible for all users of this installation. In an installation with front-end reverse proxy servers this address refers to the first front-end server that is accessible from the public network.eidm.url=https://cid.example.com/
|
| proxy.local.url (if proxy is used) | In case there is a reverse proxy server acting in front of the Ubisecure CustomerID, proxy.local.url specifies the URL that will be used by the reverse proxy when accessing the Ubisecure CustomerID. In example below, you must configure proxy to listen to eidm.url and forward requests to port 7443 on host1.localproxy.local.url=https://host1.local:7443/
|
| rest.username | The username used with REST calls. |
| rest.password | The password used with REST calls. |
| ldap.principal | The object in LDAP that is used as login object for LDAP connections from Ubisecure CustomerID. |
| ldap.password | The object in LDAP that is used as login object for LDAP connections from Ubisecure CustomerID. |
| database.host | Defines the host where PostgreSQL is installed. This can be an IP number or fully qualified domain name (FQDN). |
| database.port | Defines the public TCP port of the PostgreSQL server. Default is 5432. |
| database.name | Defines the name of the database that Ubisecure CustomerID should use from the PostgreSQL server. |
| database.user | Defines a user name that Ubisecure CustomerID should use to connect to PostgreSQL. |
| database.password | Defines the connection password for Ubisecure CustomerID database user. |
| wildfly.home | Defines the folder where WildFly is installed. |
| wildfly.http.port | Defines the TCP port where WildFly listens for unencrypted HTTP connections. |
| wildfly.https.port | Defines the TCP port where WildFly listens for encrypted HTTP connections. |
| wildfly.ip_addr.master | IP address of CustomerID master node (disregard if standalone). |
| wildfly.ip_addr.slave | IP address of CustomerID slave node (disregard if standalone). |
| wildfly.slave.password | In a HA installation the servers need to authenticate themselves in order to join the domain cluster. This password allows the customerid-slave host to connect to the domain master host. |
| database.driver.path | Defines the path where scripts can find the PostgreSQL JDBC driver. (If you have followed instructions to the letter, this must be defined to point to ~/customerid.) |
| database.driver.file | Defines the file name of the actual JDBC database driver library. |
| keystore.alias | Defines a custom alias for the server's SSL key pair in the certificate key store. |
| keystore.password | Defines a password for the key store. |
| mail.host | The DNS name or IP address of the mail server. |
| mail.port | The TCP port of the mail server. Usually 25 for SMTP. |
| mail.username | The user account name used to log on to the mail server. This is an optional field. |
| mail.password | The password of the user account name used to log on to the mail server. This is configured only in conjunction with mail.username. |
| mail.from | The email address to put in the from field of the message. |
| mail.ssl | Define if SSL should be used when contacting the mail server. Value is either true or empty. |
To run Ubisecure CustomerID setup script:
If setup.sh execution does not finish quickly, you will have to check that entropy generation settings are in order. Consult this blog post http://www.usn-it.de/index.php/2009/02/20/oracle-11g-jdbc-driver-hangs-blocked-by-devrandom-entropy-pool-empty/ for more information.
Check entropy level with cat /proc/sys/kernel/random/entropy_avail. Entropy should be over 1000.
Generate the setup configurations from templates by issuing the following commands:
cd /usr/local/ubisecure/customerid/application ./setup.sh