andwati/zitadel
1
0
Fork 0
mirror of https://github.com/andwati/zitadel.git synced 2026-10-18 05:52:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore: Service Account Naming Consistency (#11557)

Browse Source 
# Which Problems Are Solved

Inconsistent naming of service account, found in the following
variations:

  - Machine User
  - machine user
  - Service User
  - Machine Account
  - Technical Account
  - User: Type Machine

# How the Problems Are Solved

Attentive search and replace.

Localizations have been translated using Copilot

# Additional Changes

Some unused methods have been removed from the Go code.

# Additional Context

- Closes #11285
This commit is contained in:
Marco A.
2026-02-13 12:31:43 +01:00
committed by GitHub
parent 9f3d7e7bc3
commit 382aec2d61
136 changed files with 493 additions and 507 deletions
Download Patch File Download Diff File Expand all files Collapse all files
apps/docs/content/apis/migration_v1_to_v2.mdx
+1 -1
View File
@@ -98,7 +98,7 @@ No major changes have been made to the organization requests.
When migrating your user management from v1 to v2, the most significant updates involve user states and the initial onboarding process:
- **Unified User Creation Endpoint**:
- A significant simplification in v2 is the consolidation of user creation. There is now one primary endpoint for creating users, regardless of whether they are User (Human) or machine users.
- A significant simplification in v2 is the consolidation of user creation. There is now one primary endpoint for creating users, regardless of whether they are User (Human) or service accounts.
- You can use this single endpoint to provision both users (individuals interacting with your application) and service accounts (i.e. API clients), typically by specifying the user type in the request payload.
- **No More "Initial" State**:
- In v1, new users without a password or verified email were automatically assigned an initial state. This default assumption wasn't always ideal.