This document explains different scenarios for checking the password when a device locked up while configuring the site to CSO.
This is case where when we use device root password as juniper123 in device template and for the device as well. Once we give the plain-text password it will be stored in encrypted format. For juniper123, encrypted format is - $1$X.14$VKNYV2vTbJhTpqTxAeHhW/
Scenario 1:
While configuring the site to CSO, when you keep the auto populated password from the template make sure to check it is same as this string "$1$X.14$VKNYV2vTbJhTpqTxAeHhW/" which is juniper123.
Before going to submit make sure you download JSON and verify the encrypted root password is matching to this string "$1$X.14$VKNYV2vTbJhTpqTxAeHhW/". Below is the screenshot from downloaded json file.
Whenever we revisit the password field (go back and forth), just use eye button to check it. If we click on it and press any key, the password will get changed when we check in JSON. However, if we don’t press any keys, the password remains unchanged.
For example: If we add any extra space by mistake and remove it, it will ask to enter the confirm device root password. If we just copy and paste the same encrypt device password, then in downloaded JSON we might see a different encrypt root password.
CSO will think it as a plain text password, and it will be encrypted again and stored. That is the reason we see a different root password in json.
So, when this happens its better to use the original root password which was given while creating the device template 'juniper123'
Scenario 2:
While configuring the site to CSO when you enter the device root password as 'juniper123' instead of using the auto-populated encrypted one make sure you download JSON and verify the encrypted root password. In this case if you go back and forth you need to enter the password every time. Otherwise you will see a different root password in json file.