5
Hello everyone,
We have Dynamics 365 and NAV 2017, and WS-Trust authentication security protocol has been deprecated and we don' know what we should change in the standard connector for the integration between Navision 2017 (onpremise) - Dynamics 365.
Thank you very much for the help!
Thank you very much! :-)
Dynamics 365 Business Central On-Premise 17.x
Short Term Solution:
It will let the existing integration work until April 2022. Drop SDK 9.0.2.11 on the NST and update binding redirect in the server config file. Follow this link (99+) How to deploy manually the newer version of CRM SDK on premise to skip Regional Discovery Service (RDS) validation error - Dynamics 365 Business Central Forum Community Forum
Mid Term Solution:
Dynamics 365 Business Central product group is about to implement the new XRM SDK also with on-premises 17.x and it will be included in July 2021 upcoming CU.
This hotfix is related to use latest XRM SDK that allow for skipping URL verification and fall back using global discoverability service. This is a mid-term solution valid until April 2022 where legacy Office365 authentication method will be deprecated by Dynamics 365 team.
Long term solution:
Move to OAuth authentication (same as for Dynamics 365 Business Central SaaS).
Hello,
Please do have a look here:
We will update this blog today with more information how to mitigate when working with Dynamics NAV 2017 OnPrem.
Thanks.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,269
Super User 2024 Season 2
#2
Martin Dráb
230,198
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (