com.google.gerrit.extensions.client.AuthType Maven / Gradle / Ivy
// Copyright (C) 2009 The Android Open Source Project
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.
package com.google.gerrit.extensions.client;
public enum AuthType {
/** Login relies upon the OpenID standard */
OPENID,
/**
* Login relies upon the OpenID standard in Single Sign On mode
*/
OPENID_SSO,
/**
* Login relies upon the container/web server security.
*
* The container or web server must populate an HTTP header with a unique name for the current
* user. Gerrit will implicitly trust the value of this header to supply the unique identity.
*/
HTTP,
/**
* Login relies upon the container/web server security.
*
*
Like {@link #HTTP}, the container or web server must populate an HTTP header with a unique
* name for the current user. Gerrit will implicitly trust the value of this header to supply the
* unique identity.
*
*
After the authentication is done Gerrit will obtain basic user registration (name and
* email), and some group memberships, from LDP. Hence the "_LDAP" suffix in the name of this
* authentication type.
*
*
Gerrit will NOT authenticate the user via LDAP.
*/
HTTP_LDAP,
/**
* Login via client SSL certificate.
*
*
This authentication type is actually kind of SSO. Gerrit will configure Jetty's SSL channel
* to request client's SSL certificate. For this authentication to work a Gerrit administrator has
* to import the root certificate of the trust chain used to issue the client's certificate into
* the <review-site>/etc/keystore.
*
*
After the authentication is done Gerrit will obtain basic user registration (name and
* email), and some group memberships, from LDP. Hence the "_LDAP" suffix in the name of this
* authentication type.
*
*
Gerrit will NOT authenticate the user via LDAP.
*/
CLIENT_SSL_CERT_LDAP,
/**
* Login collects username and password through a web form, and binds to LDAP.
*
*
Unlike {@link #HTTP_LDAP}, Gerrit presents a sign-in dialog to the user and makes the
* connection to the LDAP server on their behalf.
*/
LDAP,
/**
* Login collects username and password through a web form, and binds to LDAP.
*
*
Unlike {@link #HTTP_LDAP}, Gerrit presents a sign-in dialog to the user and makes the
* connection to the LDAP server on their behalf.
*
*
Unlike the more generic {@link #LDAP} mode, Gerrit can only query the directory via an
* actual authenticated user account.
*/
LDAP_BIND,
/** Login is managed by additional, unspecified code. */
CUSTOM_EXTENSION,
/** Development mode to enable becoming anyone you want. */
DEVELOPMENT_BECOME_ANY_ACCOUNT,
/** Generic OAuth provider over HTTP. */
OAUTH
}