Content Manager client security
Content Manager clients connect to the Content Manager server through the Core Service, Core Service REST, IIS, or WebDAV to enable the creation or modification of Content Manager items. This section describes the right and privileges required by these clients.
The following image shows the clients of the Content Manager system:
The various clients have the different security considerations, as follows:
| Client | Description | Security considerations |
|---|---|---|
| Classic user interface | A browser-based user interface that runs as an ASP.NET web service in IIS (including a number of DLLs) and a number of JavaScript, CSS, XML and other files
Includes:
|
|
| Experience Space user interface | A browser-based user interface that runs as ASP.NET web service in IIS and a number of JavaScript, CSS, JSON and other files |
|
| Dreamweaver Templating | WebDAV Connector for Adobe Dreamweaver and WebDAV Server that integrates with ASP.NET and uses Content Manager directly | Because authentication is through IIS, using SSL/TLS is one way to secure this connection. |
| Content Porter | A Windows desktop client that communicates directly with Content Manager |
|
| Microsoft Visual Studio | .NET assembly templating through the TOM.NET API | Because it communicates with the TOM.NET API and does not use external resources, security is already handled by .NET itself. |
| TcmUploadAssembly.exe | A command-line tool that communicates directly with Content Manager |
|
| Template Builder | A Windows desktop client that communicates directly with Content Manager and uses Compound Template web service (hosted in IIS) for debugging templates |
|
| Visio Workflow Designer | A plug-in for Microsoft Visio that runs on a Windows client machine and communicates with WFListener web service (hosted in IIS) on the Content Manager server |
|
| WebDAV client | The Windows file system-based interface to the Content Manager that integrates through the WebDAV Connector with ASP.NET and uses Content Manager directly
| Because authentication is done through IIS, using SSL/TLS is one way to secure this connection. |