Domain variable not being passed to Web session

Hello,

Could you please try to modify the Username format option to {User}@{Domain} in the Advanced tab of the session's properties? And also, in the credential, please remove the @$DOMAIN$ part.



Best regards,

Hi Erica
Thank you for getting back to me. I am aware of this option.
The issue is that this works if you do the same for a new RDP session. I'm already using this way with all my RDP sessions.
And now I wanted to to the same for my Web sessions and that apparently didn't work.
This is why I posted this under Bug Report.

What you are suggesting, I would consider as a workaround, not a solution to the issue i was having/seeing :)
Do you not see this as a bug?

What is very misleading as well, is that if I where to change the setting Username format to User@Domain, it's no reflected in the Credentials Dialog(I have most Credential sessions set to "Always ask for password"). The username field is filled out correctly as User@Domain.

I might consider changing everything, but it will not be right now. So I would appreciate if this could be looked into/fixed :)

P.S. On a side note, I can't seem to find the global setting for Username format(so I can avoid having to change this for all sessions)?

Hello Brandur,

We'll investigate this issue. Does the problem only happen when you use a credential entry and link it, or does it also happen when you enter the username/domain/password directly into the Web Browser entry?

Regards,

Hi Hubert
Thanks for you patience. and sorry for the late reply.

I duplicated my session and entered the login credentials including the variables into the web session directly. This works as you would expect.
So, I can only duplicate this bug, when using/retrieving the variable in/from the Credential entry (like in my first example).
Let me know if you need anything else from me.

P.S. On a side note, I can't seem to find the global setting for Username format. Where can I find this?

Brandur,

I checked to see how the variable resolving worked, and currently it would not be possible to do what you're looking for using a variable in the credential entry. We resolve the variables in the context of the connection, not the credential. In this case, the connection's domain field is empty, which means the $DOMAIN$ variable is resolved to a blank. We will see what we can do for this but it might not be possible with how we currently do variable resolving.

This means that for now the solution is to set either the credential you are using to "username@domain" format (and set the web entry to "default"), or the web entry to "username@domain" directly.

As for the "default", let me explain how this works.
By itself, "default" doesn't force any specific username format, and it will enter the username exactly how you put it in the credentials field. If you are using a linked credential entry, though, "default" will use the credential format of that linked entry. If that linked entry's format is set to "default" this will do what is described above and not force any specific username format.

I hope this description makes it more clear what the "default" option does.

Regards,

Hubert,
Ok. If what you are saying is true. Then all my RDP sessions shouldn't work(resolve), because they are all setup in this manner. But they do :)
That is why I assumed (I know... Assuming is the mother of all fu*****) it should work for a Web session as well ;)

But it's not that big of an issue. I just reported this, because it was not behaving the same for a RDP session as it did for a Web session(my OCD kicked in).
I can change my linked credential entry's to use {User}@{Domain} and remove the @$DOMAIN$ from the Username field.
It looks like a cleaner way of doing it anyways (just my old school way of thinking, from the RDM early days).

One thing tho, that is more of a practical thing. Is that when I get the credential prompt(I have "Always ask password")[shouldn't it say "Always ask for password"?]), there is no way for me to see in what format the login is happening in.
Is there any way you could consider adding some kind af visual pointer/hint how the username is going to be inputted/interpreted ({User}@{Domain} or {Domain}\{User}) and if it's reading it from the session og the Credential entry?

Brandur,

I'll check what the difference between RDP and Web connections are, this is strange. I wouldn't have expected it to work with either of the entry types.

For the always ask for password prompt, this is a great idea. We'll see how we can add this in. :)

Regards,

Hakuna matata ;)
As I mentioned earlier, I will use your suggested method from now on.

But the indicator functionality I would love to see in the future (would make it easier for our more novice RDM users to immediately understand how the credential format are being passed to the session and from where).

Thanks again.