full URL support for Website / Web Browser session types
0 vote
I'd like the Website & Web Browser session types check the entire URL instead of FQDN.
For how it works now, when I've already logged in and I'm browsing the pages of a website, it can happen that some input fields are incorrectly filled with the username.
It would also be useful to make a difference between the website and the login page alone to create direct links to specific logins for some users.
Example:
https://www.mysite.com/ --> standard login: both admin and normal user passwords are proposed (N.2 passwords available)
https://www.mysite.com/?user=admin --> login dedicated for user with 'admin' rights (N.1 password available)
https://www.mysite.com/?user=std --> standard login is proposed (No.1 password available)
The current version dosen't check for the "/?..." part of the URL.
Hello,
So I understand correctly, is your request to support multiple URLs, each with different sets of credentials associated, all within the same entry?
Regards,
Hubert Mireault
Hello
please refer to this for further details: https://devolutions.atlassian.net/servicedesk/customer/portal/1/DEVO-8156
Hi,
To be able to do this, you need to compare the url with a regex.
In your case:
1.
For the website session with the URL https://www.mysite.com/?user=admin
Set the Compare Type in your session to "Compare regex with full URL"
Write the Regex: ^(http[s]:\/\/www\.mysite\.com\/?)(?:\?user=admin)?$
2.
For the website session with the URL https://www.mysite.com/?user=std
Set the Compare Type in your session to "Compare regex with full URL"
Regex: ^(http[s]:\/\/www\.mysite\.com\/?)(?:\?user=std)?$
Let us know if it works for you.
Best regards,
Olivier Désalliers
Hi Olivier.
as i sayd in the support ticket i linked, that doesn't work with Chrome, nor with Firefox.
Hi,
By not working, do you mean that it is still matching urls that it shouldn't?
Could you send me via Private Messages some exemples of real case urls (they don't need to work in our environment), the ones you want to get matches, some you don't want to get matches and the regex in your sessions, so we can analyse them.
For the issues with the wrong inputs/fields filled, you can write the username id and password id in the HTML Control ID section when using a Web Browser session or in More settings in case you are using a Website session. This way, only the fields with the username id and password id that are matching the ones in the session will be automatically filled on load.
https://help.remotedesktopmanager.com/troubleshooting_webauthentication.htm
https://help.remotedesktopmanager.com/troubleshooting_webauthentication.htm#method-2
Best regards,
Olivier Désalliers
Hi
oh wow.
it seems it's working ok now.
I read the latest release notes, but didn't notice a reference to this enhancement.
I'm very sorry for the time wasted.