I’m have credentials created for various group of servers which can be replaced by the real value from the custom properties and values like this: $Env.USERNAME$@mygroup#$CustomProperty.Address$@$CustomProperty.Servername$.
This credential are used by connection however I see this is printed literally during the connection.
Hi Amresh,
do I understand correctly that the connection is working, but the value is being printed in clear text, or are the token names printed?
Would you also be able to share a screen recording / screenshots of your configuration (whilst hiding all sensitive information), so we can look into this?
If you want, you can also create a new Support Ticket here, and we will get back to you directly:
https://www.royalapps.com/go/support-ticket-new
Best regards,
Christoph
Hi Amresh,
thanks for the screenshot.
Could you please also share screenshots of your Credential and the Custom Properties sections, whilst hiding all sensitive information?
Furthermore, I will move your thread to the Royal TSX (macOS) forum.
Best regards,
Christoph
Thanks Christoph. Attached you’ll find my credential setting, folder level setting and individual server settings for custom fields and properties.
Hi Amresh,
thanks for the screenshots.
May I ask if the correct username is taken or if the string “$Env.USERNAME$@mygroup#$CustomProperty.Address$@$CustomProperty.Servername$.” is used as the username value?
Best regards,
Christoph
The string “$Env.USERNAME$@mygroup#$CustomProperty.Address$@$CustomProperty.Servername$.” is used as the username value.
Hi Christoph, would you able to find the root cause of the issue and how to solve this?
I was wondering if someone has faced this or can provide some solution? Is there a way to escalate?
Hi Amresh,
sorry for not getting back to you yet.
I was able to reproduce the behavior within Royal TSX V6, and we are currently looking into this.
Best regards,
Christoph
Thanks. Appreciate it!
Is there any resolution planned for it?
Hi Amresh,
unfortunately, I currently don’t have any news regarding this topic and cannot promise you if and when this behavior will be adjusted.
Once it has been adjusted, we will update the thread.
Best regards,
Christoph
*Knock Knock*
It been over couple of month’s and I was wondering if this was created as a support ticket as Chirstoph mentioned? This helps in knowing if this is not forgotten :)!
Hi Amresh,
I’m happy to report that this is now working as expected in our internal Royal TSX V6 Build.
The changes will be made available in the upcoming Royal TSX V6 Beta Build.
Unfortunately, I currently don’t have a release date for you regarding this, however, you can enable “Automatically check for updates” and “Include Beta releases” to be notified, once a new Royal TSX Beta is available:
Thank you for your patience, and sorry for not getting back to your earlier.
Best regards,
Christoph
Thanks Christoph. Looks like with the new updates, I have this working now except one part. I have cyberArk integration where I provide the UserName for connection in this format: $Env.USERNAME$@mygroup#$CustomProperty.Address$@$CustomProperty.Servername$. Here $Env.USERNAME is vault user taken from system’s ENV variable. All custom property and group tokens are getting replaced fine on Windows machine however $Env.USERNAME doesn’t work on Mac. Is there a way where the system user name (which in my case is a vault user) can be fetched from the env variables or by some other means?
Hi Amresh,
I’ve spoken to our lead-dev regarding this and on macOS there is the possibility to set environmental variables for all applications globally, however, this is very hacky and not really supported. See https://stackoverflow.com/questions/135688/setting-environment-variables-on-os-x
Another possibility is to start Royal TSX with certain environmental variables.
If, for example, you have the environmental variables stored in your bash or zsh profile and start Royal TSX via terminal, the environmental variables should also be available within Royal TSX.
You would then have to start via
/Applications/Royal\ TSX.app/Contents/MacOS/RoyalTSX
For example, if you open a terminal and enter the following:
export TESTIP="10.0.1.40”
and then start Royal TSX via /Applications/Royal\ TSX.app/Contents/MacOS/RoyalTSX, you can use******$Env.TESTIP$ as the computer name in a terminal connection and access your server 10.0.1.40
To summarize, your use case is possible to access, but you have to make sure that the environmental variables you need are also available in the context of Royal TSX.
Best regards,
Christoph