import jakarta.validation.constraints.Size;

/**
 * Form class for editing file authentication configurations in the admin interface.
 * This form extends CreateForm to include fields necessary for updating existing file authentication entries,
 * including tracking information for optimistic locking and audit trails.
 * File authentication configurations define access control for file system crawling operations.
 *
 */

     * @since 3.0-beta-1
     */
    boolean isProjectAware();

    /**
     * @param authentication authentication
     * @since 3.0-alpha-3
     */
    void setAuthentication(Authentication authentication);

    /**
     * @return repository authentication
     * @since 3.0-alpha-3
     */
    Authentication getAuthentication();

    /**
     * @param proxy proxy
     * @since 3.0-alpha-3

import org.codelibs.fess.app.web.admin.webauth.EditForm;

/**
 * Request body class for web authentication edit operations in the admin REST API.
 * This class extends EditForm to inherit the necessary form validation and binding capabilities
 * for web authentication management operations.
 */
public class EditBody extends EditForm {

    /**
     * Default constructor.
     */

::: fastapi.security.APIKeyHeader

::: fastapi.security.APIKeyQuery

## HTTP Authentication Schemes

::: fastapi.security.HTTPBasic

::: fastapi.security.HTTPBearer

::: fastapi.security.HTTPDigest

## HTTP Credentials

::: fastapi.security.HTTPAuthorizationCredentials

::: fastapi.security.HTTPBasicCredentials

## OAuth2 Authentication

::: fastapi.security.OAuth2

    * A cookie.
* `http`: standard HTTP authentication systems, including:
    * `bearer`: a header `Authorization` with a value of `Bearer ` plus a token. This is inherited from OAuth2.
    * HTTP Basic authentication.
    * HTTP Digest, etc.
* `oauth2`: all the OAuth2 ways to handle security (called "flows").
    * Several of these flows are appropriate for building an OAuth 2.0 authentication provider (like Google, Facebook, X (Twitter), GitHub, etc):

    }

    @Test
    @DisplayName("Test log authentication success")
    void testLogAuthentication() {
        logger.logAuthentication(true, "testuser", "DOMAIN", "192.168.1.1");

        Map<EventType, Long> stats = logger.getStatistics();
        assertEquals(Long.valueOf(1), stats.get(EventType.AUTHENTICATION_SUCCESS), "Should have 1 authentication event");
    }

    @Test

/**
 * Interface for authentication chain operations.
 * Provides methods for user management and authentication operations.
 */
public interface AuthenticationChain {

    /**
     * Updates an existing user in the authentication chain.
     * @param user The user to update.
     */
    void update(User user);

    /**
     * Deletes a user from the authentication chain.
     * @param user The user to delete.

/**
 * SPNEGO response token (NegTokenTarg) used in SPNEGO authentication exchanges
 */
public class NegTokenTarg extends SpnegoToken {

    /**
     * Result code indicating unspecified result
     */
    public static final int UNSPECIFIED_RESULT = -1;
    /**
     * Result code indicating authentication completed successfully
     */
    public static final int ACCEPT_COMPLETED = 0;
    /**

    }

    /**
     * Gets the array of supported authentication mechanisms
     * @return the mechanisms array
     */
    public ASN1ObjectIdentifier[] getMechanisms() {
        return this.mechanisms;
    }

    /**
     * Sets the array of supported authentication mechanisms
     * @param mechanisms the mechanisms to set
     */

import jcifs.util.Crypto;
import jcifs.util.Hexdump;

/**
 * For initiating NTLM authentication (including NTLMv2). If you want to add NTLMv2 authentication support to something
 * this is what you want to use. See the code for details. Note that JCIFS does not implement the acceptor side of NTLM
 * authentication.
 *
 */
public class NtlmContext implements SSPContext {