Symptoms:
- I have a Unity Version Control (formerly known as Plastic SCM) cloud organization with encryption enabled. I entered the wrong encryption key and then checked in some changes to the cloud repository.
- I used the incorrect encryption key when checking in changes. What do I do?
Cause:
If you have checked in/pushed some changes to a cloud repository with the wrong encryption key, this will prevent your team from downloading these file revisions.
Resolution:
A fast workaround is to delete the changeset created with the wrong encryption key. Then delete your local crypteservers.conf and finally restart the Unity Version Control (Plastic SCM) GUI. The next time you perform a checkin/push, you are required to enter the encryption key again.
If you cannot easily delete the affected changeset, you can perform a new checkin creating new revisions for the affected files. Before performing the new checkin, be sure that your encryption key is fixed and you are using the right one.
With this second workaround, you are fixing the problem in the head of the branch, but the previous revisions are still inaccessible, so any replica operations or trying to access the old content will not work. WE DO NOT RECOMMEND THIS OPTION.
To reset your local encryption configuration so that you are requested to enter the key again when the Unity Version Control GUI is restarted, delete the below files (when you restart the UVCS GUI, you are requested to enter the key again):
C:\Program Files\PlasticSCM\server\cryptedservers.conf (server-side encryption configuration)
C:\Users\{User}\AppData\Local\plastic4\cryptedservers.conf(client-side encryption configuration)