- Überblick
- Erste Schritte
- Konzepte
- Verwenden der UiPath CLI
- Anleitungen
- CI/CD-Rezepte
- Befehlsreferenz
- Überblick
- Exitcodes
- Globale Optionen
- UIP-codierter Agent
- uip coder
- uip context-grounding
- UIP-Dokumentation
- uip function
- uip guardrails
- uip llm-configuration
- uip llm-gateway
- uip model-hub
- Add-Test-Data-Entität
- Add-Test-Data-Queue
- Add-Test-Data-Variation
- Analysieren
- Erstellen
- Ein Projekt erstellen
- Diff
- Suchaktivitäten
- Get-Analyse-Regeln
- get-standard-aktivität-xaml
- Fehler abrufen
- Manuelle-Testfälle erhalten
- Manuelle-Testschritte erhalten
- get-library-object-repository
- get-object-repository
- Get-Versionen
- Beispiel für einen Workflow abrufen
- Anwendung anzeigen
- Anzeigeelement
- Inspektionspaket
- install-data-fabric-entities
- Pakete installieren oder aktualisieren
- list-data-fabric-entities
- list-instances
- Beispiele für Listenworkflows
- Packen
- Veröffentlichen
- remote
- restore
- run, debug & execution
- Ausführungsdatei installieren
- Suchvorlagen
- Studio starten
- Ausführung anhalten
- tm
- UIA
- uip tasks
- UIP-Ablaufverfolgungen
- uip traces feedback
- Migration
- Referenz und Support
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.
Zusammenfassung
uip user
uip user
uip user honors the global options (--output, --output-filter, --log-level, --log-file). Exit codes follow the standard contract.
Argumente
Keine.
Optionen
Keine über die globalen Optionen hinaus.
Beispiel
uip user
uip user
Datenform (--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.
Zugehörig
- 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.