Royal TS V6 - Shared Document with individual authentification
M
Martin Binder
started a topic
over 1 year ago
Hello together,
we use a shared document to give all team members access to our servers and applications using a general account for authentification. However, it is sometimes necessary to use user-specific account information for authentication for certain servers, which leads to the situation that the general user information in the server enty is being overwritten with the specific user information in the shared document.
Does anyone know a way to use the shared document as a central passport management tool in the team, but still work with individual accounts if necessary?
Thank you in advance for sharing your experiences.
Best regards
Martin
Best Answer
C
Christoph Muehlberger
said
over 1 year ago
Hi Martin,
to achieve this, all you need to do is change the way you have configured the credential. Change the setting to "Specify a Credential Name" and then define a credential name for this connection.
For this example, let's call the credential "Credential 1":
Then have all your team members have to create a separate private credential document. In that document, they need to create a new credential called "Credential 1" where they define their own credentials for that connection.
The idea is that you don't actually configure any credentials in the shared document; you just specify credential names. Then, everyone has to create their own credentials with the names specified in the shared document.
Please note that both documents (shared document and private credential document) have to be open at the same time for this to work.
You can find step-by-step examples of configuring this here:
to achieve this, all you need to do is change the way you have configured the credential. Change the setting to "Specify a Credential Name" and then define a credential name for this connection.
For this example, let's call the credential "Credential 1":
Then have all your team members have to create a separate private credential document. In that document, they need to create a new credential called "Credential 1" where they define their own credentials for that connection.
The idea is that you don't actually configure any credentials in the shared document; you just specify credential names. Then, everyone has to create their own credentials with the names specified in the shared document.
Please note that both documents (shared document and private credential document) have to be open at the same time for this to work.
You can find step-by-step examples of configuring this here:
Martin Binder
Hello together,
we use a shared document to give all team members access to our servers and applications using a general account for authentification. However, it is sometimes necessary to use user-specific account information for authentication for certain servers, which leads to the situation that the general user information in the server enty is being overwritten with the specific user information in the shared document.
Does anyone know a way to use the shared document as a central passport management tool in the team, but still work with individual accounts if necessary?
Thank you in advance for sharing your experiences.
Best regards
Martin
Hi Martin,
to achieve this, all you need to do is change the way you have configured the credential. Change the setting to "Specify a Credential Name" and then define a credential name for this connection.
For this example, let's call the credential "Credential 1":
Then have all your team members have to create a separate private credential document. In that document, they need to create a new credential called "Credential 1" where they define their own credentials for that connection.
The idea is that you don't actually configure any credentials in the shared document; you just specify credential names. Then, everyone has to create their own credentials with the names specified in the shared document.
Please note that both documents (shared document and private credential document) have to be open at the same time for this to work.
You can find step-by-step examples of configuring this here:
https://www.royalapps.com/go/kb-all-teamsharing
Alternatively, you can also use the "Overrides' feature, which is described here:
https://www.royalapps.com/go/blog-ts-winmac-overrides
I hope this helps!
Best regards,
Christoph
Christoph Muehlberger
Hi Martin,
to achieve this, all you need to do is change the way you have configured the credential. Change the setting to "Specify a Credential Name" and then define a credential name for this connection.
For this example, let's call the credential "Credential 1":
Then have all your team members have to create a separate private credential document. In that document, they need to create a new credential called "Credential 1" where they define their own credentials for that connection.
The idea is that you don't actually configure any credentials in the shared document; you just specify credential names. Then, everyone has to create their own credentials with the names specified in the shared document.
Please note that both documents (shared document and private credential document) have to be open at the same time for this to work.
You can find step-by-step examples of configuring this here:
https://www.royalapps.com/go/kb-all-teamsharing
Alternatively, you can also use the "Overrides' feature, which is described here:
https://www.royalapps.com/go/blog-ts-winmac-overrides
I hope this helps!
Best regards,
Christoph
1 person likes this
-
What happened to the forum?
-
About this Forum
-
Security Information
-
Supported Secure Gateway (SSH) ciphers
-
Why is no remote file browser in SCP available?
-
What encryption is used in the rtsz files when enabled?
-
Royal TS V4 License File
-
How to resolve RDP resolution issues in Windows 7 with high resolution screen
-
Auto Fill in web page connection
-
How to reference custom properties in tasks and templates?
See all 260 topics