Username format using basic authentication for Web Browser
Hi there,
I've read on your forum that you implemented domain support for basic authentication about 8 years ago. However, I like to use one credential for a lot of connections. Some require a domain and some do not. Now I see one combination that doesn't work:
Credential object includes username, domainname and password.
Using Web Browser object.
- Using forms-based auth, the domainname is not filled by default
- Using forms-based auth in combination with Advanced > Username format > {Domain}\{User}, the domainname is filled
- Using basic auth, the domainname is filled by default
- Using basic auth in combination with Advanced > Username format > {User}, the domainname is still being filled.
The last situation is unwanted for me. Can you tell me if this is a misconfiguration on my side, or that ignoring the domain is not possible by design for basic authentication?
Greetings,
Dennis
All Comments (12)
Hello,
Would you be able to send a link that we can access where the issue occurs, we will have a look.
Best Regards,
Etienne Lord
Hello,
Thank you for contacting us on this matter. I would like to gather a bit more information about your environment to help me assist you.
What version of RDM do you use?
What is the type of data source you use?
Also, could you please send us screenshots of the following?
- The properties of your entry in RDM
- The unwanted behavior itself, to make sure we avoid any confusion.
Best regards,
Gabriel Degrandpré
What version of RDM do you use?
What is the type of data source you use?
Also, could you please send us screenshots of the following?
- The properties of your entry in RDM
- The unwanted behavior itself, to make sure we avoid any confusion.
RDM Free version 2020.2.13.0 64-bit
Datasource type SQLite
Credential:
Connection "Web Browser" with linked credentials
The basic authentication is set
Username format specified to ignore the domain:
As a result, the "DOM" domain is still used in basic authentication
2020-06-22 07_58_04-Window.png
2020-06-22 07_54_33-Window.png
2020-06-22 07_53_41-Window.png
2020-06-22 07_52_37-Window.png
2020-06-22 07_51_44-Window.png
Hello,
I have verified the code and this is not the expected behavior. I'm not sure why this is happening but we will fix this for sure.
Regards
David Hervieux
By the way, if you have small sample (we don't need reel credential or url) it will be even easier to reproduce and test. You seems to have an example that you could export and post.
Regards
David Hervieux
Thank you!
Attached you'll find the test objects.
_DevolutionsTest.rdm
Hello,
This issue is now fixed internally. It will be included in version 2020.2.15.0.
Regards
Jonathan Del Signore
This issue is now fixed internally. It will be included in version 2020.2.15.0.
Thank you for the fast support and also the implemented fix. Great job!
Dennis
This solution works for the browsers Default, Internet Explorer and Chrome but not for Firefox at my system. I'm not using Firefox, but thought you might want to know this.
Hello,
Thank you for this information, it has been transmitted to our Engineering Department.
Best regards,
James Lafleur
Hello,
Our Engineering Department just informed me that this issue has been solved for Firefox as well.
The fix should be available in RDM 2020.2.17.
Best regards,
James Lafleur
Great job, as always!