| | |
|---|
| | | * Windows authentication
|
|---|
| | | * PAM authentication
|
|---|
| | | * Htpasswd authentication
|
|---|
| | | * HTTP header authentication
|
|---|
| | | * Redmine auhentication
|
|---|
| | | * Salesforce.com authentication
|
|---|
| | | * Servlet container authentication
|
|---|
| | |
|---|
| | | realm.authenticationProviders = htpasswd
|
|---|
| | | realm.htpasswd.userFile = /path/to/htpasswd
|
|---|
| | |
|
|---|
| | | ### HTTP Header Authentication
|
|---|
| | |
|
|---|
| | | HTTP header authentication allows you to use existing authentication performed by a trusted frontend, such as a reverse proxy. Ensure that when used, gitblit is ONLY availabe via the trusted frontend, otherwise it is vulnerable to a user adding the header explicitly.
|
|---|
| | |
|
|---|
| | | By default, no user or team header is defined, which results in all authentication failing this mechanism. The user header can also be defined while leaving the team header undefined, which causes users to be authenticated from the headers, but team memberships to be maintained locally.
|
|---|
| | |
|
|---|
| | | realm.httpheader.userheader = REMOTE_USER
|
|---|
| | | realm.httpheader.teamheader = X-GitblitExample-GroupNames
|
|---|
| | | realm.httpheader.teamseparator = ,
|
|---|
| | | realm.httpheader.autoCreateAccounts = false
|
|---|
| | |
|
|---|
| | | ### Redmine Authentication
|
|---|
| | |
|
|---|
| | | You may authenticate your users against a Redmine installation as long as your Redmine install has properly enabled [API authentication](http://www.redmine.org/projects/redmine/wiki/Rest_Api#Authentication). This user service only supports user authentication; it does not support team creation based on Redmine groups. Redmine administrators will also be Gitblit administrators.
|
|---|
