I am integrating RDM 2023.1.14.0 (not really important). I can extract the Web URLs e.g. rdm://open?DataSource=9EA27266-45xxxxxDF&Repositoryxxx &Session=84906xxxxF00 and am exporting them to a helpdesk solution (osticket).
My problem is when I open the ticket, the web brower (Chrome and Edge) changes the URL to denied:rdm://open?DataSource=9E..... so I can not open it.
If I open the link in a new browser window and remove the denied: part, RDM will open as expected and works perfectly.
So this is not really an RDM problem. However, if someone can give me a hint what I'm missing to stop Chome / Edge from adding "denied:" and just open RDM on a click, I would be very happy. (I have tried to allow "insecure content" in Edge for [*.]open with no result. I can not work out how to set up Chrome to do the same as it only seem to allow "proper" URL (e.g. https://company.com) to be added to insecure content, not anything that starts with RDM://
Thanks in advance.
Maybe have a look to see if Protocol Handlers have been blocked/denied in your Chrome/Edge configuration.
This is the first time I've seen something like this. Very interested to see and understand what is going on here.
Best regards,
Stéfane Lavergne
Yes by default all considered "unsafe" links are disabled. I don't know how to tell chrome and edge to add the url to the exception list as the rdm: extension is not accepted.
I can't reproduce the issue on my side. Can you try the following?
Best regards,
Stéfane Lavergne
test2.html