Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
W
Warden
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Pavel Valach
Warden
Commits
49e4a8fb
Commit
49e4a8fb
authored
7 years ago
by
Pavel Kácha
Browse files
Options
Downloads
Plain Diff
Merge branch 'warden-3' of homeproj.cesnet.cz:warden into warden-3
parents
c4b7bdd6
14990104
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
warden3/warden_server/README
+13
-2
13 additions, 2 deletions
warden3/warden_server/README
with
13 additions
and
2 deletions
warden3/warden_server/README
+
13
−
2
View file @
49e4a8fb
...
@@ -123,7 +123,8 @@ particular implementation object of the aspect, for example type of logger
...
@@ -123,7 +123,8 @@ particular implementation object of the aspect, for example type of logger
Log: FileLogger, SysLogger
Log: FileLogger, SysLogger
DB: MySQL
DB: MySQL
Auth: X509Authenticator, PlainAuthenticator
Auth: X509Authenticator, X509NameAuthenticator,
X509MixMatchAuthenticator,PlainAuthenticator
Validator: JSONSchemaValidator, NoValidator
Validator: JSONSchemaValidator, NoValidator
Handler: WardenHandler
Handler: WardenHandler
...
@@ -144,7 +145,17 @@ object from particular section list is used ("FileLogger" for example).
...
@@ -144,7 +145,17 @@ object from particular section list is used ("FileLogger" for example).
X509Authenticator: authenticate based on certificate chain validation,
X509Authenticator: authenticate based on certificate chain validation,
hostname corresponding with certificate CN or SubjectAltName and
hostname corresponding with certificate CN or SubjectAltName and
optionally shared secret
optionally shared secret (note that more clients on one machine
will have to have the certificate with the same hostname, clients
than can be differentiated by separate secrets).
This method is OBSOLETE.
X509NameAuthenticator: authenticate based on certificate chain validation,
certificate CN must correspond with client _name_, NOT hostname.
X509MixMatchAuthenticator: automatically choose X509Authenticator or
X509NameAuthenticator based on existence of 'secret' in query. Allows
for seamless transition of clients between two authentication methods.
PlainAuthenticator: authenticate based on client name or shared secret, usable
PlainAuthenticator: authenticate based on client name or shared secret, usable
over plain HTTP connection or HTTPS without client certificate - note that
over plain HTTP connection or HTTPS without client certificate - note that
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment