Some web clients are not cookie-aware and do not send the session cookie back to Airlock Gateway (WAF). This could result in too many sessions on Airlock Gateway (WAF) or the authentication flow not working. To provide a solution for such clients, the following must be configured:
- Airlock Gateway (WAF): In the application Mapping, the Session handling must be configured to Sessionless.
- Airlock Gateway (WAF): The Denied access URL and the Authentication flow must be configured for One-Shot.
- Airlock IAM: Must be configured for authentication flow One-Shot (see Front-Side Kerberos configuration (one-shot flow) ).
An example of such a web application is WebDAV. The Windows client is not cookie aware, so the mentioned configuration must be applied.