It is recommended that you disable API Security if you are working with a Non-Domain Workgroup.
-
Media Publisher server on non-Domain Workgroup and service running as a local user with access to the storage location for media files:
-
APISecure="false" (found in the <Application> section)
-
Security mode="None" (case-sensitive - found in the <wsHttpBinding>/<Security> section)
-
Transport Client = "None" (case-sensitive - found in the <wsHttpBinding>/<Security>/<Transport> section)
-
-
The Minutes Client is running on a different machine:
-
Security mode="None" (case-sensitive - found in the <wsHttpBinding>/<Security> section)
-
Transport Client="None" (case-sensitive - found in the <wsHttpBinding>/<Security>/<Transport> section)
-
It is also recommended to disable API Security if working across two different Domains (not under the same Domain Forest).
-
Media Publisher server on Domain A, and service running as a Domain user with access to the storage location for media files:
-
APISecure="false" (found in the <Application> section)
-
Security mode="None" (case-sensitive - found in the <wsHttpBinding>/<Security> section)
-
Transport Client="None" (case-sensitive - found in the <wsHttpBinding>/<Security>/<Transport> section)
-
-
Minutes Client running on different machine and different Domain:
-
Security mode = "None" (case-sensitive)
-
Transport Client = "None" (case-sensitive)
-
The use of a Domain User when on a Domain, or Local User when on a Local Workgroup is recommended to run the Media Publisher Service. If no domain user is specified during the Media Publisher installation, the service is set to run as Local System, which works only if the storage location for media files is on the same machine as the Media Publisher service. Running as Local System gives the service elevated permissions and is less secure. Setting the user as Network Service also works, but port 1955 would need to be reserved specifically for Network Service. Running it as network service has lower privileges than Local System, but has no credentials so is less secure.
For details of the configurations supported by Microsoft®, consult the following URL: https://msdn.microsoft.com/en-us/library/ff648863.aspx. https://msdn.microsoft.com/en-us/library/ff648863.aspx. https://msdn.microsoft.com/en-us/library/ff648863.aspx