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 archives (EARs).
To download Identity Provider metadata and generate Service Provider metadata:
...
Download IDP metadata by running the following commands:
Code Block | ||||
---|---|---|---|---|
| ||||
cd /D "%PROGRAMFILES%\Ubisecure\customerid\tools\"
get-metadata.cmd |
This command will show download statistics if successful.
...
Initialize Ubisecure CustomerID SPs by running the following commands:
Code Block | ||||
---|---|---|---|---|
| ||||
cd /D "%PROGRAMFILES%\Ubisecure\customerid\tools\"
init-eidm-sp.cmd |
This command will not display any output if successful.
Initialize authentication provider by running the following commands:
Code Block | ||||
---|---|---|---|---|
| ||||
cd /D "%PROGRAMFILES%\Ubisecure\customerid\tools\"
init-eidm-ap.cmd |
...
.
Deploy the Ubisecure CustomerID applications to WildFly using the deploy-ear.cmd script. When invoking the script, you must supply the path to the ear file, like in the example below:
...