Ubisecure CustomerID uses WildFly as a J2EE Container. This chapter describes how to download Identity Provider metadata from Ubisecure SSO, generate Service Provider metadata, and deploy the cid-ear-x.x.x.ear and cid-worker-ear-x.x.x.ear enterprise ear enterprise archives (EARs).
To download Identity Provider metadata and generate Service Provider metadata:
Download IDP metadata by running the following commands:
| Code Block | ||||
|---|---|---|---|---|
| ||||
cd /usr/local/ubisecure/customerid/tools
./get-metadata.sh |
Initialize Ubisecure CustomerID SPs by running the following commands:
| Code Block | ||||
|---|---|---|---|---|
| ||||
cd /usr/local/ubisecure/customerid/tools
./init-eidm-sp.sh |
Initialize authentication provider by running the following commands:
...
| language | text |
|---|---|
| theme | RDark |
...
.
...
Deploy the Ubisecure CustomerID applications to WildFly using the deploy-ear.sh command. When invoking the command, you must supply the path to the ear file, like in the example below:
| Code Block | ||||
|---|---|---|---|---|
| ||||
cd /usr/local/ubisecure/customerid/tools ./deploy-ear.sh ~/customerid/cid-ear-x.x.x.ear ./deploy-ear.sh ~/customerid/cid-worker-ear-x.x.x.ear |
...