REST iControl account password issue if special characters used

​Sorry, false alarm, it turned out that it wasn't a password special character issue at all.  I was updating my script to include REST logons (in addition to the SOAP logons that are already present in the script) and that broke because the account I was using has a dynamically changing token which caused the REST logon to fail since the token can't be reused (at least in any reasonable amount of time).  Note that I'm not referring to the token that a REST logon returns after a successful logon (and can be reused for whatever the timeout period is  - 8 hours I believe).

This does bring up another question, however.  We have many independent clusters of F5s which all are set to authenticate against the same TACACS+ servers.  As mentioned above, all accounts use dynamically changing tokens.  There are many cases where I use the script to logon to multiple F5 clusters to perform various activities and it would be really nice if there was some way to authenticate against one cluster and then use the returned REST token (or some other mechanism) to logon to other F5 clusters so that I wouldn't have to enter a new token to each F5 cluster.  Is there any way of doing that?