com.aerospike.client.policy.AuthMode Maven / Gradle / Ivy

Go to download

Show more of this group Show more artifacts with this name
Show all versions of aerospike-client-bc-jdk8 Show documentation

Aerospike Java client interface to Aerospike database server. Uses Bouncy Castle crypto library for RIPEMD-160 hashing.

There is a newer version: 9.0.0

Show newest version

/*
 * Copyright 2012-2021 Aerospike, Inc.
 *
 * Portions may be licensed to Aerospike, Inc. under one or more contributor
 * license agreements WHICH ARE COMPATIBLE WITH THE APACHE LICENSE, VERSION 2.0.
 *
 * 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.aerospike.client.policy;

/**
 * Authentication mode.
 */
public enum AuthMode {
	/**
	 * Use internal authentication when user/password defined. Hashed password is stored
	 * on the server. Do not send clear password. This is the default.
	 */
	INTERNAL,

	/**
	 * Use external authentication (like LDAP) when user/password defined. Specific external
	 * authentication is configured on server. If TLS defined, send clear password on node
	 * login via TLS. Throw exception if TLS is not defined.
	 */
	EXTERNAL,

	/**
	 * Use external authentication (like LDAP) when user/password defined. Specific external
	 * authentication is configured on server.  Send clear password on node login whether or
	 * not TLS is defined. This mode should only be used for testing purposes because it is
	 * not secure authentication.
	 */
	EXTERNAL_INSECURE,

	/**
	 * Authentication and authorization based on a certificate.  No user name or
	 * password needs to be configured. Requires TLS and a client certificate.
	 * Requires server version 5.7.0+
	 */
	PKI
}