Le contenu n'est pas disponible dans la langue sélectionnée.
Setting up a secure connection to the Core Service
You can set up one or more types of secure connections to the Core Service by editing specific configuration files.
Setting up HTTPS connections to the Core Service To be able to connect securely through HTTPS, SOAP-compatible clients, including the SDL Content Porter client, require a change to the server-side configuration of certain bindings. Custom client applications built by your organization also require the same changes in the client-side configuration.
Securing the Core Service net.tcp endpoints Clients that connect to the Core Service through its net.tcp endpoints are typically custom code running in the context of the Content Manager Explorer Web site or the Experience Manager Web site (as part of a GUI extension). Such code is assumed to be running on the same machine as the Core Service itself. As a result, by default, the net.tcp port is closed on your firewall to prevent all net.tcp connections from outside.