In this mode Authentick will be acting as reverse proxy in front of the third-party application. Your third-party application will not need to be exposed to the internet directly.
This mode supports immediate session suspension. If a user logs out, Authentick Proxy is immediately aware of it.
The third-party application will receive a signed JWT assertion which identifies the currently logged-in user. Authentick Proxy can be used in combination with other authentication modes.
Authentick Proxy requires you to configure an Internal as well as a public hostname.
Internal hostname: Defines what host Authentick should connect to. This needs to include the HTTPS or HTTP protocol. (example:
Public hostname: Defines what the public hostname is that should be routed to the internal endpoint. (example:
Authentick will add the following headers to the request:
X-Forwarded-For: Containing the original client IP address
X-Gatekeeper-Jwt-Assertion: Containing the JWT assertion.
In the application settings you will find the following details:
You usually do not need to change these in the future.