Web Application Proxy
Copy link to the page “Web Application Proxy”Replaces certificates on the WAP federation listener, selected published applications, or both.
What happens
- The service agent on the server fetches the task from the appliance over outbound HTTPS, port 443.
- The Windows basics first import the certificate into the Windows certificate store (LocalMachine\My).
- The certificate is assigned to the WAP federation listener and/or the selected published applications. If it fails: Rollback puts the previous certificates back.
- Verification: the integration checks configuration and served TLS certificates for the changed roles on this node and the other cluster nodes.
Technical details
- Connection
- The integration runs through the service agent on the server. The service agent connects over outbound HTTPS to the appliance, port 443 by default. You open no port into the server.
- Service ports
- 443
- What you need
- The service agent installed on the server.
- Platform
- Windows Server 2012 R2 and later
- Actions
- Discovery, Installation, Verification, Rollback
- Integrations
-
windows-wap1.2.0 - Note
-
- Discovery finds WAP configuration, federation and application certificates and certificates in the server store. Rollback restores only changed roles that still use the deployment certificate. In a WAP cluster with several nodes an application's certificate applies to every node; the integration changes it only with SharedApplicationChange=allow, once the certificate is imported on each node.