- Visão geral
- Introdução
- Conceitos
- Usando o UiPath CLI
- Guias de instruções
- Receitas de CI/CD
- Referência de comando
- Visão geral
- Códigos de saída
- Opções globais
- Agente de código uip
- uip coder
- uip context-grounding
- Documento da UIP
- uip function
- uip guardrails
- uip llm-configuration
- uip llm-gateway
- uip model-hub
- adicionar-tipo-dados-de-teste
- adicionar-dados-de-teste-fila
- adicionar-teste-variação de dados
- Analisar
- Criar
- criar projeto
- Comparação
- encontrar atividades
- obter-analisador-regras
- obter-padrão-atividade-xaml
- obter-erros
- obter-casos-de-teste-manuais
- obter-etapas-de-teste-manual
- get-library-object-repository
- get-object-repository
- Obter versões
- obter-fluxo-de-trabalho-exemplo
- indicar aplicativo
- indicar elemento
- inspecionar pacote
- instalar-data-fabric-entities
- instalar-ou-atualizar pacotes
- listar-data-fabric-entities
- list-instances
- listar-exemplos-de-fluxo-de-trabalho
- Empacotar
- Publicar
- remote
- restore
- run, debug & execution
- arquivo de execução
- modelos-pesquisar
- Iniciar Studio
- interromper a execução
- tm
- UIA
- uip tasks
- Traces da UIP
- uip traces feedback
- Migração
- Referência e suporte
Syntax and options for `uip user`, which shows identity information about the currently logged-in session.
uip user shows who the current session is authenticated as — a whoami for uip. It takes no arguments and no options beyond the global ones.
Resumo
uip user
uip user
uip user honors the global options (--output, --output-filter, --log-level, --log-file). Exit codes follow the standard contract.
Argumentos
Nenhum.
Opções
Nenhuma além das opções globais.
Exemplo
uip user
uip user
Formato dos dados (--output json)
{
"Code": "User",
"Data": {
"UserId": "a1b2c3d4-0000-0000-0000-000000000001",
"Name": "Jane Doe",
"Username": "jane.doe@my-org",
"Email": "jane.doe@my-org.com",
"FirstName": "Jane",
"LastName": "Doe"
}
}
{
"Code": "User",
"Data": {
"UserId": "a1b2c3d4-0000-0000-0000-000000000001",
"Name": "Jane Doe",
"Username": "jane.doe@my-org",
"Email": "jane.doe@my-org.com",
"FirstName": "Jane",
"LastName": "Doe"
}
}
The fields are parsed straight out of the session's access token claims. When the active session is an application (client-credentials) session rather than a human user, there is no person behind it — UserId/Name/Username/Email/FirstName/LastName come back as empty strings, but the response also includes IdentityType (identifying it as an application identity) and ClientId, so a script can distinguish "no user data" from "not actually a user."
Failure behavior
- Not logged in:
AuthenticationError, exit code2, withInstructionspointing touip login. - Session present but the login-status check itself fails (for example, a corrupted credentials file):
ConfigError, exit code1.
Relacionado
- uip login — start the session
uip userreports on. - uip login status — session-level detail (org, tenant, expiration) rather than user identity.
- Authentication — the credential model behind the session.