Feature: Add Support for Custom auth-token validation #188
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it
Add Support for Custom auth-token validation
If
openvpn.auth-token-user
is enabled, the server will push the auth-token to the client, and finish quickly recover when the client is recovering from wakeupre-auth is also benefited from this PR, there will be a very quick re-auth even without enabling
oauth2.refresh.enabled
20s delay for autorization after process restart #144 is also benefited from this PR if
oauth2.refresh.enabled
is disabledWhich issue this PR fixes
Special notes for your reviewer
TODO: configurable AUTH-TOKEN lifetime checker
Particularly user-facing changes
Please ensure to remove
auth-gen-token
from your OpenVPN server configuration to make this workChecklist
Complete these before marking the PR as
ready to review
: