Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
G
go-sso
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
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
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
id
go-sso
Commits
8ed88638
Commit
8ed88638
authored
5 years ago
by
ale
Browse files
Options
Downloads
Patches
Plain Diff
Add allowed_groups to sso-proxy docs
parent
fe763606
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+4
-1
4 additions, 1 deletion
README.md
with
4 additions
and
1 deletion
README.md
+
4
−
1
View file @
8ed88638
...
@@ -120,7 +120,8 @@ it wouldn't be safe for them to trust this information anyway, unless
...
@@ -120,7 +120,8 @@ it wouldn't be safe for them to trust this information anyway, unless
they have a way to ensure it comes only from the trusted sso-proxy
they have a way to ensure it comes only from the trusted sso-proxy
(perhaps using TLS or other forms of transport verification). Finally,
(perhaps using TLS or other forms of transport verification). Finally,
*sso-proxy*
only handles incoming requests based on their Host
*sso-proxy*
only handles incoming requests based on their Host
attribute, not the request path.
attribute, not the request path. And the only access control rules
currently supported are group-based.
The proxy server has its own configuration file,
*/etc/sso/proxy.yml*
The proxy server has its own configuration file,
*/etc/sso/proxy.yml*
by default, which has the following attributes:
by default, which has the following attributes:
...
@@ -135,6 +136,8 @@ by default, which has the following attributes:
...
@@ -135,6 +136,8 @@ by default, which has the following attributes:
*
`backends`
is the list of configured endpoints and associated
*
`backends`
is the list of configured endpoints and associated
backends, each entry has the following attributes:
backends, each entry has the following attributes:
*
`host`
the HTTP host to serve
*
`host`
the HTTP host to serve
*
`allowed_groups`
is a list of the groups whose users will be
allowed access to the service
*
`upstream`
is a list of
*host:port*
addresses for the upstream
*
`upstream`
is a list of
*host:port*
addresses for the upstream
backends
backends
*
`tls_server_name`
allows you to explicitly set the value of the
*
`tls_server_name`
allows you to explicitly set the value of the
...
...
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