diff --git a/ui/src/RegenerateAccountTokenModal.tsx b/ui/src/RegenerateAccountTokenModal.tsx index 596c20e3..827d7809 100644 --- a/ui/src/RegenerateAccountTokenModal.tsx +++ b/ui/src/RegenerateAccountTokenModal.tsx @@ -84,18 +84,25 @@ const RegenerateAccountTokenModal = ({ close, isOpen, user }: RegenerateAccountT - You will need to manually edit your ${HOME}/.zrok/environment.json files - (in each environment) to use the new zrok_token. Updating these files will restore - the functionality of your environments. + You will need to use the zrok rebase accountToken command to update any enabled + environments to use your new account token. Rebasing your environments will minimize any service + disruptions caused by regenerating your account token. - Alternatively, you can just zrok disable any enabled environments and re-enable - using the updated account token. Running zrok disable before you regenerate will + Keep in mind that once you've regenerated your account token, any running zrok share + or zrok access processes may not be able to interact with the zrok service properly + until they are restarted. + + + + + Alternatively, you can just zrok disable any enabled environments and re-enable + using the updated account token. Running zrok disable before you regenerate will delete your environments and any shares they contain (including reserved shares). So if you have - environments and reserved shares you need to preserve, your best option is to update the zrok_token in - those environments as described above. + environments and reserved shares you need to preserve, your best option is to use the + zrok rebase accountToken command as described above. { successMessage ? null : controls }