Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Domainname/%username%
#21
Will be released in the next days :-)
Regards/Gruss
Oliver
Reply
#22
Sorry to highjack the thread, I have a similiar but also different use case.
We are implementing Bastion PAM (from Wallix) and the goal is that all RDP connections go through one Bastion instance, meaning the destination is for all connection the same.
The bastion is though capable by finding the correct destination server if you specify this info in the username.
The username needs to look something like this in order to be working:
%USERNAME%@exampledomain.com@exampleWinServer:RDP:%USERNAME%

Since every administrator has their personalized username and password, I would need ASG to be able to store inside the credential the above line as an username and still allow admins to put their personal value, without having to create a credential object for each server.

As usable variables I could use:
1. Connection Name (for us it equals hostname, meaning the credential object could put the "exampleWinServer" value
2. Username


Thank you very much in advance and very kind Regards!
Reply
#23
Ok added %ConnectionName% for use in credential objects...
Regards/Gruss
Oliver
Reply
#24
(20-02-2020, 12:02 PM)DevOma Wrote: Ok added %ConnectionName% for use in credential objects...

Thank you for your quick reply.
And what about the %Username% variable that is also needed?
Reply
#25
%Username% was added already :-)
Regards/Gruss
Oliver
Reply
#26
(20-02-2020, 05:01 PM)DevOma Wrote: %Username% was added already :-)

Thank you but in your documentation I can see it is only viable with external applications. We need this for multiple RDP Connections, without any RD Gateway, that the username inside the credential object is the variable.

For me it seems ASG does not support this scenario, which I just confirmed with testing it.
If ASG supports this feature could you explain me where to find the info on how to use it?
Reply
#27
It is part of release 2020 - will be released very soon
Regards/Gruss
Oliver
Reply
#28
(21-02-2020, 10:47 AM)DevOma Wrote: It is part of release 2020 - will be released very soon

Thank you very much for implementing it in the next release. I tested it and I can say it works partially.
Unfortunately it supports only the use of 1 variable in the username (credential object), not multiple like I would need it.

This is my current username field:
%LoginUsername%@%LoginDomain%@%ConnectionName%:RDP:%LoginUsername%@%LoginDomain%

It always just resolved the Username, if I just use one variable it resolves correctly.

Thank you very much!
Reply
#29
I will check asap - and if corrected you can use a private build of course...
Regards/Gruss
Oliver
Reply
#30
(24-02-2020, 03:01 PM)DevOma Wrote: I will check asap - and if corrected you can use a private build of course...

any update on this?

Edit: Just noticed the pm. sorry
Reply
#31
I send you the link to the private build via Private Message!
Regards/Gruss
Oliver
Reply
#32
(27-02-2020, 11:52 AM)DevOma Wrote: I send you the link to the private build via Private Message!

Yeah i noticed this as well later. Sorry for this.
With the private build it is fully working!
Now I am experimenting if the variables are working under ssh within a commandline, but I'm still preparing a lot and don't know how the bastion and ASG need to work together (yet)

But it would be nice to know if variables work under SSH in the commandline. Let me know Smile


Kind Regards
Reply
#33
Whenever you "Connect" via ASGRD the variables should be resolved - independent which protocol you use...
Regards/Gruss
Oliver
Reply
#34
(24-02-2020, 03:01 PM)DevOma Wrote: I will check asap - and if corrected you can use a private build of course...
Hi,

can I get the private build too? I'm a Wallix customer as well. 

Kind regards
Christian
Reply
#35
Send you a PM
Regards/Gruss
Oliver
Reply




Users browsing this thread: 1 Guest(s)