You’re offline. This is a read only version of the page.
105
We have an on-premise customer whose CRM has been enabled for IFD. It's hosted locally and exposed through Claims Based Authentication (ADFS).
However, there are some .NET web extensions deployed in the same IIS as CRM that are not loading for internet facing users (but load fine when users connected to VPN).
When customer presses the link for the Web Extension in dynamics, the URL is servername:81/.../Default.aspx .
How can these Web Extensions be enabled for access in IFD?
Hi AMD99.
I think a good start would be to provide the output(mask if needed) of e.g. DevTools - Network tab from the web browser when loading this extension.
However, you say that it works for users connected via VPN but not for any others.. so are you sure this CRM Web Extension website is exposed to the ones not connected via VPN, e.g Internet?
So to elaborate on this.
You have your CRM IFD url which is probably something like "https://<crmorgname>.company.com" as https(port:443) should be used if exposed outside your perimeter network e.g. the Internet and then you have your extension website on "">servername:81/.../default.aspx"
A user working from a remote network will never be able to reach servername:81 as it's considered a "local" address, it will basically try to look this address up on the users LAN and if not connected to VPN, it will simply not reach this url.
When connected to the VPN however, the client pc simplified, is basically considered sitting on the corporate network thus reaching servername:81.
Hope this helps!
Best regards.
Philip
Share
Report
All responses (
Answers (
