-
-
Notifications
You must be signed in to change notification settings - Fork 27
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* add does an IAP handle non-HTTP traffic to FAQ
- Loading branch information
Showing
1 changed file
with
17 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
--- | ||
title: "How does an Identity-Aware Proxy handle non-HTTP traffic?" | ||
description: "It does not handle non-HTTP traffic because it’s designed to work with OAuth 2." | ||
tags: | ||
- Identity-Aware Proxy | ||
- non-HTTP traffic | ||
- OAuth 2 | ||
- VPN | ||
--- | ||
|
||
## Question | ||
|
||
If we use an Identity-Aware Proxy (IAP), how does it handle non-HTTP traffic? | ||
|
||
## Answer | ||
|
||
IAP does not handle non-HTTP traffic because it’s designed to work with OAuth 2, which is strictly an HTTP-based authentication scheme. Non-HTTP traffic must flow over SSH tunnels or via a VPN (e.g. OpenVPN). |