With Master Encryption, we have introduced these passwords:
1. Master Password:
	> this is set via admin console ONCE. 
	> The master password should NEVER change!!!
	> the master password is encrypted with session password, and save in DB.
	> when there is a new session key, the db value must be updated;
2. Session Password
	> This password is used to encrypt the master password
3. Subscriber Encryption Password:
	> This is auto generated for each subscriber;
	> This is encrypted by master password before saving the db
	> This is stored in encrypted form in SubscriberBO. 
	> The clear form is only used for one decrpytion run and then discarded. 
	  The clear form is NEVER long term stored in RAM.
	  
	  
Deployment Notes:
Before deployment:
> Prepare a JDK-1.7.80 with unlimited JCE strength:
	For ALL slaves:
		for each slave:
			install the jdk
			change /etc/profile to the new JAVA_HOME
			restart the slave (BEFORE the deployment). Wait for it to come back online	
	For all servers:
		1. install the jdk
		2. change /etc/profile to the new JAVA_HOME
		3. MUST change jboss/run.conf to use proper jdk

		
During deployment:
	1. Before switch 37 to main, check: if we can decrypt the previously encrypted CC data.
	2. Generate private/public for all users.		