There are several preconfigured values that you must change, for security reasons,
after a fresh installation. You must set a new password for the universal user (customer ID
100) and configure the password in the configuration accordingly.
Prerequisites
To enable strong cryptography, download the Java
Cryptography Extension (JCE) unlimited strength jurisdiction policy file from your JDK
vendor and update the security policy JAR files within the JVM that is running
SAP Mobile Platform Server. Task
Note: The SQL command in step 6 is for an Adaptive Server® Enterprise database. For DB2
and Oracle database, substitute the appropriate SQL syntax.
- Navigate to:
SMP_HOME\Server\tools\mobiliser\com.sybase365.mobiliser.vanilla.cli-tools-5.1.3.RELEASE-CLIPasswordEncoderClient.jar
- From a command line, execute:
java -jar
com.sybase365.mobiliser.vanilla.cli-tools-5.1.3.RELEASE-CLIPasswordEncoderClient.jar
- Select the hashing method.
- Enter the plain password.
- May not be required, depending on the hashing method you selected, enter the
salt.
- In the database, update the hash value by running:
UPDATE "MOB_CUSTOMERS_CREDENTIALS" SET STR_CREDENTIAL = '<Hash
Value>' WHERE ID_CUSTOMER = 100
- Update the creation date for both the universal user (customer ID 100) and sysmgr
user (customer ID 106) with:
| Database |
States |
|---|
| ASE |
UPDATE MOB_CUSTOMERS_CREDENTIALS SET DAT_CREATION = GETDATE()
WHERE ID_CUSTOMER IN (100,106) |
| DB2 |
UPDATE MOB_CUSTOMERS_CREDENTIALS SET DAT_CREATION =
CURRENT_TIMESTAMP WHERE ID_CUSTOMER IN (100,106) |
| Oracle |
UPDATE MOB_CUSTOMERS_CREDENTIALS SET DAT_CREATION = SYSDATE WHERE
ID_CUSTOMER IN (100,106) |