[Cloud] Wrong encryption key used.

Question:

I have a Plastic SCM cloud organization with encryption enabled. I entered the wrong encryption key and then checked in some changes to the cloud repository.

Answer:

If you have checked in/pushed some changes to a cloud repository with the wrong encryption key, this is going to cause issues for the rest of the team as they won't be able to download these file revisions.

1) A fast workaround is deleting the changeset created with the wrong encryption key. Then delete your local "crypteservers.conf" and finally restart the Plastic GUI.

This way, the next time you perform a checkin/push, you will be requested to enter the encryption key again.

2) If you cannot easily delete the "broken" changeset, you can perform a new checkin creating new revisions for the "broken" 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 will fixing the problem in the head of the branch, but the previous revisions will be still broken (created with the wrong encryption key). 

To reset your local encryption configuration so that you are requested to enter the key again when the Plastic GUI is restarted, please delete the below files (when you restart the Plastic 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)