20-05-2020, 09:20 AM
(This post was last modified: 20-05-2020, 05:26 PM by WOPS.
Edit Reason: missing words in a sentence
)
We have the centralized managed environments.xml (%ProgramData%\ASG-RemoteDesktop\13.0) on our Terminal Server Session Host. The Environment.xml contains multiple Database entries for different IT Teams. Every ASG database has its own permissions for the particular team (ASG security groups). The environments.xml has more than 15 entries and every entry has its own database.
When pass trough authentication is disable in ASG and I try to connect to a database where I have no permission, I get a message “connection could not be established” and I have to select another entry from the “loin to…” screen. When I have pass through authentication enabled and I have connection established to my database. Then I start the environment manager to select another DB entry where I have no permission, ASG close and start again and tries to logon to the database where I have no permission. I get same message “connection could not be established” but the different is that I am in a pass through authentication loop.
A workaround is to edit the users profile.xml set <PassThroughLogin>true</PassThroughLogin> to false or change the <CurrentEnvironment>DB No permission</CurrentEnvironment> to the old value.
Is it possible for a future update to get the user the opportunity in the GUI to disable pass through authentication that the user can select another entry, where the user has permission to?
Normally the ASG user does not know where the XML is and the user is able edit the XML itself, even if he or she has a little bit XML syntax knowledge :-).
Best regards,
Daniel
When pass trough authentication is disable in ASG and I try to connect to a database where I have no permission, I get a message “connection could not be established” and I have to select another entry from the “loin to…” screen. When I have pass through authentication enabled and I have connection established to my database. Then I start the environment manager to select another DB entry where I have no permission, ASG close and start again and tries to logon to the database where I have no permission. I get same message “connection could not be established” but the different is that I am in a pass through authentication loop.
A workaround is to edit the users profile.xml set <PassThroughLogin>true</PassThroughLogin> to false or change the <CurrentEnvironment>DB No permission</CurrentEnvironment> to the old value.
Is it possible for a future update to get the user the opportunity in the GUI to disable pass through authentication that the user can select another entry, where the user has permission to?
Normally the ASG user does not know where the XML is and the user is able edit the XML itself, even if he or she has a little bit XML syntax knowledge :-).
Best regards,
Daniel
