Tel que `/users/me`, disons pour récupérer les données sur l'utilisateur actuel.

Et vous avez un second chemin : `/users/{user_id}` pour récupérer de la donnée sur un utilisateur spécifique grâce à son identifiant d'utilisateur

Les *fonctions de chemin* étant évaluées dans l'ordre, il faut s'assurer que la fonction correspondant à `/users/me` est déclarée avant celle de `/users/{user_id}` :

Algo como `/users/me` por exemplo, digamos que essa rota seja utilizada para pegar dados sobre o usuário atual.

E então você pode ter também uma rota `/users/{user_id}` para pegar dados sobre um usuário específico associado a um ID de usuário.

Porque as operações de rota são avaliadas em ordem, você precisa ter certeza que a rota para `/users/me` está sendo declarado antes da rota `/users/{user_id}`:

        assertEquals(expected, auth.isPreferredMech(oid));
    }

    @Test
    @DisplayName("Accessors: user/realm/service and lifetimes")
    void accessors_workAsExpected() {
        Kerb5Authenticator auth = new Kerb5Authenticator((Subject) null);

        // User accessors
        assertNull(auth.getUser());
        auth.setUser(null);
        assertNull(auth.getUser());
        auth.setUser("");

    // ============================================================

    /** Property key for user information configuration. */
    public static final String USER_INFO_PROPERTY = "user.info";

    /** Property key for user favorite functionality configuration. */
    public static final String USER_FAVORITE_PROPERTY = "user.favorite";

    /** Property key for search log configuration. */

Wants=network-online.target
After=network-online.target opensearch.service
Requires=opensearch.service

[Service]
Environment=FESS_HOME=${packaging.fess.home.dir}
EnvironmentFile=-${packaging.env.file}

User=${packaging.fess.user}
Group=${packaging.fess.group}

ExecStart=${packaging.fess.bin.dir}/fess

# Connects standard output to /dev/null
StandardOutput=null

# Connects standard error to journal
StandardError=journal

MinIO batch jobs framework also provides

- Retrying a failed job automatically driven by user input
- Monitoring job progress in real-time
- Send notifications upon completion or failure to user configured target

Following YAML describes the structure of a replication job, each value is documented and self-describing.

```yaml
replicate:
  apiVersion: v1

        }
        return null;
    }

    /**
     * Performs logout operations for the specified user using SSO.
     *
     * @param user The user to logout
     * @return The logout URL from the SSO authenticator, or null if SSO is not available
     */
    public String logout(final FessUserBean user) {
        if (available()) {
            final SsoAuthenticator authenticator = getAuthenticator();

adding an OwnerReference

A vulnerability exists in the NodeRestriction admission controller where node users can delete their corresponding node object by patching themselves with an OwnerReference to a cluster-scoped resource. If the OwnerReference resource does not exist or is subsequently deleted, the given node object will be deleted via garbage collection. By default, node users are authorized for create and patch requests but not delete requests against their node object. Since the NodeRestriction...

import org.codelibs.fess.opensearch.user.exentity.Group;
import org.codelibs.fess.opensearch.user.exentity.User;
import org.lastaflute.web.Execute;
import org.lastaflute.web.response.JsonResponse;

import jakarta.annotation.Resource;

/**
 * API action for admin group management.
 * Provides RESTful API endpoints for managing user group settings in the Fess search engine.

        runtime.registerData("adminUser",
                fessConfig.isAdminUser(username) || fessLoginAssist.getSavedUserBean()
                        .map(user -> user.hasRoles(fessConfig.getAuthenticationAdminRolesAsArray()))
                        .orElse(false));

        runtime.registerData("pageLoginLink", fessConfig.isLoginLinkEnabled());
    }