...
In Windows, unzip the Zip archive into the C:\Ubisecure folder.
| Code Block |
|---|
| language | text |
|---|
| theme | RDark |
|---|
| title | Unpacking TUPAS Emulator on Windows |
|---|
|
cd /d c:\ubisecure
unzip tupasemulator.zip |
...
In Linux, unpack the Tar archive into the /usr/local/ubisecure folder.
| Code Block |
|---|
| language | text |
|---|
| theme | RDark |
|---|
| title | Unpacking TUPAS Emulator on Linux |
|---|
|
cd /usr/local/ubisecure
gzip -dc tupasemulator.tar.gz | tar xvf - |
...
The .war file in the TUPAS Emulator software package does not contain any configuration settings. Before deployment the configuration file must be merged into the .war file. The TUPAS Emulator software package includes a command to simplify merging the .war file and the configuration file:
| Code Block |
|---|
| language | text | theme |
|---|
| RDark | title | Merging on Windows |
|---|
|
cd /d c:\ubisecure
mergetupasemulator.cmd |
| Code Block |
|---|
| language | text |
|---|
| theme | RDark |
|---|
| title | Merging on Linux |
|---|
|
cd /usr/local/ubisecure
sh mergetupasemulator.sh |
As a result of the merge command the merged .war file is created into the webapps folder. Copy the merged .war file to the webapps directory in the Tomcat installation directory:
| Code Block |
|---|
| language | text | theme | RDark |
|---|
| title | Windows |
|---|
|
cd /d c:\ubisecure\webapps
copy tupasemulator.war "C:\Program Files\apache-tomcat-5.5.17\webapps" |
| Code Block |
|---|
| language | text |
|---|
| theme | RDark |
|---|
| title | Linux |
|---|
|
cd /usr/local/ubisecure/webapps
copy tupasemulator.war /usr/local/apache-tomcat-5.5.17/webapps |
...
Add an TUPAS Emulator authentication object to your Ubisecure LDAP directory with the import script from Ubisecure Server Installation. You will need the file methods.ldif. After installing UAS according to document SSO Installation, this file will be in directory c:\Ubisecure\ldap (Windows environment) or /usr/local/ubisecure/ldap (Linux environment). From this file, copy the part that contains "Tupas 2, test" to a new file named tupasemulator.ldif.
| Code Block |
|---|
| language | text | theme | RDark |
|---|
| title | Example of tupasemulator.ldif |
|---|
|
Tupas 2, Test dn:
cn=tupas.test.1,cn=Server,ou=System,cn=Ubilogin,dc=localhost
changetype: add
cn: tupas.test.1
objectClass: top
objectClass: ubiloginAuthMethod
ubiloginAuthMethodType: Tupas 2
ubiloginClassname: com.ubisecure.auth.login.Tupas2LoginModule
ubiloginConfString: alg 01
ubiloginConfString: idtype 02
ubiloginConfString: keyvers 0001
ubiloginConfString: langcode FI
ubiloginConfString: macKey1 LEHTI
ubiloginConfString: rcvid 87654321
ubiloginConfString: url http://localhost:8080/tupasemulator/
ubiloginConfString: vers 0002
ubiloginEnabled: FALSE
ubiloginTitle: Tupas Test |
Choose the import script according to your platform and Ubisecure LDAP directory. Execute the following commands to create the TUPAS Emulator authentication object in the Ubisecure LDAP directory.
| Code Block |
|---|
| language | text |
|---|
| theme | RDark |
|---|
| title | Initializing Ubisecure Directory and TUPAS Emulator in Windows |
|---|
|
cd /d c:\ubisecure\ldap
openldap\import.cmd tupasemulator.ldif |
| Code Block |
|---|
| language | text | theme | RDark |
|---|
| title | Initializing Ubisecure Directory and TUPAS Emulator in Linux |
|---|
|
cd /usr/local/ubisecure/ldap
sh openldap/import.sh tupasemulator.ldif |
...