Assign a security access policy for HTTP and HTTPS endpoints
If you apply a run-as policy and the service manifest declares HTTP endpoint resources, you must specify a SecurityAccessPolicy. SecurityAccessPolicy ensures that ports allocated to these endpoints are correctly restricted to the user account that the service runs as. Otherwise, http.sys does not have access to the service, and you get failures with calls from the client. The following example applies the Customer1 account to an endpoint called EndpointName, which gives it full access rights.
<Policies>
<RunAsPolicy CodePackageRef="Code" UserRef="Customer1" />
<!--SecurityAccessPolicy is needed if RunAsPolicy is defined and the Endpoint is http -->
<SecurityAccessPolicy ResourceRef="EndpointName" PrincipalRef="Customer1" />
</Policies>
For an HTTPS endpoint, also indicate the name of the certificate to return to the client. You reference the certificate using EndpointBindingPolicy. The certificate is defined in the Certificates section of the application manifest.
<Policies>
<RunAsPolicy CodePackageRef="Code" UserRef="Customer1" />
<!--SecurityAccessPolicy is needed if RunAsPolicy is defined and the Endpoint is http -->
<SecurityAccessPolicy ResourceRef="EndpointName" PrincipalRef="Customer1" />
<!--EndpointBindingPolicy is needed if the EndpointName is secured with https -->
<EndpointBindingPolicy EndpointRef="EndpointName" CertificateRef="Cert1" />
</Policies>
Warning
When using HTTPS, do not use the same port and certificate for different service instances (independent of the application) deployed to the same node. Upgrading two different services using the same port in different application instances will result in an upgrade failure. For more information, see Upgrading multiple applications with HTTPS endpoints .
For next steps, read the following articles: