Changed CRM binding URL from Http to Https:
Server includes a few organizations.
Sound easy, why should be complex with this definition? Only add 's' to the http and change the port from 5555 to 443.
If you need to do it don't forget to start in Development environment then QA and after check all system in Production
The first thing is to arrange the list we all the required changes.
I created my task and I assume your tasks should be the same -/+.
1. Changing Binding Type in Deployment Tool
2. Define binding in IIS Microsoft Dynamics CRM site to work Https + add certification.
Create a valid Certificate and don’t forget to remove the http records.
3. Register: under HLM\SOFTWARE\Microsoft\MSCRM, change manual the ServerUrl to Https
4. Jobs: Change CRM URL in app Config.
5. User Windows Services: I assume app config contains CRM URL change
connections.
6. Custom Website that opens CRM pages for instance invokes CRM pages or requesting CRM SDK: update web.config
7. Update code/configuration file in custom website that CRM call to services from this sites.
Site from binding HTTPS call to service from HTTP binding for instance WCF can be security problem.
Another example calls window.openModalDialog unable to get response to CRM in JS.
8. SSIS update parameters.
9. Java Script: check in all file if use hard coded http.
10. Plugins the same search for hard coded.
11. Configuration file. Almost every CRM implementation contain configuration entity change records if needed
12. Telephone integration or third company which calls to CRM should change the path.
13. Open port in firewall. I assume 443.
This is not easy special if Dynamics CRM exists a few years but can be done. :-)
Thanks,
Rami Heleg.
+972-52-5695114
