Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
Add
openconnect_get_auth_expiration
function to library and JNI
This allows protocols to save the moment when a session's authentication (`vpninfo->cookie`) is expected to expire and no longer be useful for reconnection. The motivation is to eventually allow front-ends to know whether reauthentication is needed, or whether they should try using a cached cookie. Current state: - AnyConnect protocol: expiration is determined from the CONNECT response header `X-CSTP-Session-Timeout-Remaining` (with `X-CSTP-Session-Timeout` or `X-CSTP-Lease-Duration` as upper bounds in its absence) - GlobalProtect protocol: expiration is determined from the `<lifetime>` tag of the XML config. - Juniper Network Connect protocol: no currently known way to determine expiration. The `DSID` cookie is a standard HTTP cookie, so perhaps its expiration timestamp is intended for this purpose; however, I can find no real-world case where it has an expiration timestamp set. - None of the currently-supported protocols provide the expiration timestamp until the connection phase, so it can't be obtained for export by the `--authenticate` option. Signed-off-by: Daniel Lenski <dlenski@gmail.com>
- Loading branch information
Showing
10 changed files
with
60 additions
and
1 deletion.
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
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
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
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
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
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
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
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
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
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