White Label Whatfix with Proxy Server Integration
- 26 Feb 2025
- 1 Minute To Read
-
Print
-
DarkLight
-
PDF
White Label Whatfix with Proxy Server Integration
- Updated On 26 Feb 2025
- 1 Minute To Read
-
Print
-
DarkLight
-
PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
In enterprise environments, security and branding hold paramount importance. For organizations with strict Content Security Policies (CSPs), any policy change requires multiple reviews and can prove time-consuming and inefficient. To address such concerns, Whatfix enables white labeling of end user API requests via a proxy server, removing all references to Whatfix. Your end users do not see any references to Whatfix thus reinforcing your brand identity and maintaining a consistent and professional appearance. Additionally, the integration enables the implementation of additional security measures on the proxy server to safeguard end users from potential threats.
Here’s how the integration works.
Consider a user on the underlying application who needs help. The user launches Self Help for assistance and this normally sends a message directly to Whatfix. However, with this new proxy server integration, that message first goes to a dedicated server, similar to a mailroom. The mailroom server has several important functions:
The proxy server transforms the request to reflect your company's identity, a process known as white labeling.
The proxy server can implement additional security protocols, such as authentication and authorization checks, before forwarding the request to Whatfix. On receiving the request, Whatfix processes it and transmits the relevant information back to the proxy server.
Finally, the mailroom server delivers the answer to the user on the website, ensuring everything appears consistent with the brand. All content, such as images or videos are delivered via the proxy server and remains the central point of control for all communication.
This architecture provides a secure, branded, and controlled integration with Whatfix, shielding end users from any direct interaction with the third-party service.
The following GIF illustrates the data requests between end users, proxy server, and Whatfix:
Implementation considerations
Once you’ve implemented this integration, here are some things to consider:
Proxy Server Infrastructure: You need to have a proxy server infrastructure in place that can handle the volume of API requests from your end users.
Configuration: Proper configuration of the proxy server is essential to ensure that requests are routed correctly and that security measures are properly enforced.
Maintenance: Ongoing maintenance and monitoring of the proxy server is crucial to ensure optimal performance and security.
Note:
To set up this integration, contact support@whatfix.com.
Was this article helpful?