Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 10512

Re: Getting Error in Mobiliser 5.1

$
0
0

Hello,

 

I have been able to successfully get it working but the encryption needs to be handled in a particular manner.

 

The mobiliser id (user 100) needs to have an encrypted password of your choosing.  The encrypted value for whatever plain text password you choose is obtained using the com.sybase365.mobiliser.vanilla.cli-tools-5.1.3.PL01-CLIPasswordEncoderClient.jar file which is in the {MOBILISER_HOME}/tools directory.  Once that value is obtained it needs to be placed in the MOB_CUSTOMERS_CREDENTIALS table, in the row where the mobiliser id is located.  (The default value before changing is REPLACE_ME).

 

Once this is done and the dates for that row have been updated, to ensure that the account is not in an expired state, you will need to create another encrypted value for the preferences which is based off of the plain SAME plain text value.  This is done using the com.sybase365.mobiliser.vanilla.cli-tools-5.1.3.PL01-CLIEncrypterClient.jar file which is also located in the {MOBILISER_HOME}/tools directory.  This jar file is used in the following way:

 

Usage: encrypt <key> <text>

 

where <key> is a decryption key that is chosen by you (Remember This Key it will be used again)

where <text> MUST be the plain text value that you used for the mobiliser user

 

The result of this encryption will be placed in the MOB_PREFERENCES table in the STR_VALUE column where STR_PATH =

 

/presentationlayer/system/com/sybase365/mobiliser/util/tools/wicketutils/services/Configuration/

and /presentationlayer/system/com/sybase365/mobiliser/web/util/DynamicServiceConfiguration/

 

 

Finally you must update your WEB UI context.xml file to use the correct value to decrypt the preferences password.  This value is the same as the <key> value specified earlier.  The value needs to be used in plain text in the context.xml file which looks like:

 

<Environment description="The prefs secret key" name="prefs/secret"

    type="java.lang.String" value="<key>" />

 

This will need to be done for BOTH portals.

 

Let me know if there is anything unclear and I will try my best to simplify


Viewing all articles
Browse latest Browse all 10512


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>