// Test with different names
        LdapUser user2 = new LdapUser(testEnv, "anotheruser");
        assertEquals("anotheruser", user2.getName());

        // Test with empty name
        LdapUser user3 = new LdapUser(testEnv, "");
        assertEquals("", user3.getName());

        // Test with null name
        LdapUser user4 = new LdapUser(testEnv, null);
        assertNull(user4.getName());
    }

    @Test

        User user1 = createTestUser("user1", "User One");
        User user2 = createTestUser("user2", "User Two");
        User user3 = createTestUser("user3", "User Three");

        chain.update(user1);
        chain.update(user2);
        chain.update(user3);

        assertEquals(3, chain.updateCalls.size());
        assertEquals(user1, chain.updateCalls.get(0));

        User user2 = createTestUser("user2");
        User user3 = createTestUser("user3");

        TestAuthenticationChain chain1 = new TestAuthenticationChain();
        TestAuthenticationChain chain2 = new TestAuthenticationChain();
        TestAuthenticationChain chain3 = new TestAuthenticationChain();

        chain1.loadResult = user1;
        chain2.loadResult = user2;
        chain3.loadResult = user3;

import org.codelibs.fess.Constants;
import org.codelibs.fess.entity.FessUser;
import org.codelibs.fess.mylasta.direction.FessConfig;
import org.codelibs.fess.opensearch.user.bsentity.BsUser;
import org.codelibs.fess.util.ComponentUtil;

/**
 * @author FreeGen
 */
public class User extends BsUser implements FessUser {

    private static final long serialVersionUID = 1L;

    private String originalPassword;

        assertFalse(exception1.getMessage().equals(exception2.getMessage()));
        assertEquals("User is not found: user1", exception1.getMessage());
        assertEquals("User is not found: user2", exception2.getMessage());
    }

openapi: 3.0.3
info:
  title: Fess - User API
  description: |-
    This is a Fess Server based on the OpenAPI 3.0 specification.  
  license:
    name: Apache 2.0
    url: http://www.apache.org/licenses/LICENSE-2.0.html
  version: 14.8.0
externalDocs:
  description: API Documentation
  url: https://fess.codelibs.org/14.8/api/
servers:
  - url: http://localhost:8080/api/v1
tags:
  - name: search
    description: Search operations

        assertEquals("user1", resultList.get(0).get("name"));
    }

    @Test
    public void test_register_collectionPerformanceOptimization() {
        RenderData data = new RenderData();

        BsUser entity1 = new BsUser();
        entity1.setName("user1");
        BsUser entity2 = new BsUser();
        entity2.setName("user2");

    }

    /**
     * Redirects an authenticated user to the appropriate admin interface based on their roles.
     * Users with admin roles are redirected to the dashboard, while other users are redirected
     * to their designated admin action class or to the root if no specific action is available.
     *
     * @param user the authenticated user bean containing role information

     * Handles user authentication setup and database persistence.
     * If the surname is blank, it will be set to the user's name.
     *
     * @param user the user entity to store
     */
    public void store(final User user) {
        final String username = user.getName();
        final boolean isUpdate = StringUtil.isNotBlank(user.getId());

        if (logger.isDebugEnabled()) {

Although properties offer the benefit of precise user-side control and support gradual evolution practices, the high number of properties also presents challenges.

The main challenge on the user side is comprehensibility.
With that many properties, and considering the tendency for properties to accrete in user builds over time, it is important for users to understand the contracts tied to the features.