HTCondorWiki: Upgrading To Eight Nine Twelve

 
 {subsection: Step 2: Compatibility changes with IDTOKENS}
 
-We fixed a bug in how the IDTOKENS authentication method reads its signing key(s), which are stored in directory =/etc/condor/passwords.d=.  If you created these signing key(s) by using the _condor_store_cred_ command-line tool, you should not have any problems.  If, however, you created the signing key file(s) in directory =/etc/condor/passwords.d= via some other method (such as a copying from =/dev/random=), there is a possibility that previously issued tokens will no longer authenticate.  In this case, we recommend that you re-issue these tokens to clients via either _condor_token_create_ or _condor_token_fetch_.
+We fixed a bug in how the IDTOKENS authentication method reads its signing key(s), which are stored in directory =/etc/condor/passwords.d=.  If you are not currently using tokens, or you have created these signing key(s) by using the _condor_store_cred_ command-line tool, you should not have any problems and can skip to Step 3.  If, however, you created the signing key file(s) in directory =/etc/condor/passwords.d= via some other method (such as a copying from =/dev/random=), there is a possibility that previously issued tokens will no longer authenticate.  In this case, we recommend that you re-issue these tokens to clients via either _condor_token_create_ or _condor_token_fetch_.
 
 {subsection: Step 3: Directory permission changed in /etc/condor/tokens.d}