✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Greptile Overview

Greptile Summary

This PR renames the API parameter subOrganizationName to organizationSlug across all identity login endpoints (Universal Auth, LDAP, JWT, OIDC, AWS IAM, Azure, GCP, Kubernetes, Alicloud, OCI, TLS Cert, and Token Auth). This is a breaking API change.

Key Changes:

• Renamed parameter from subOrganizationName to organizationSlug in 13 authentication router endpoints
• Updated corresponding TypeScript type definitions across all identity auth services
• Modified business logic in service layers to use the new parameter name
• Updated error messages to reference "slug" instead of "name" (e.g., "Sub organization with slug X not found")
• Enhanced API documentation description to be more descriptive about parameter behavior
• The underlying database query logic remains unchanged (still queries by slug field)

Breaking Change Impact:

• Any API clients using subOrganizationName parameter will receive validation errors
• According to the PR description, this won't affect existing users since sub-organization access is currently restricted
• The change affects all 13 identity authentication methods consistently

Confidence Score: 5/5

• This PR is safe to merge - it's a straightforward parameter rename with consistent changes across all authentication methods
• The changes are mechanical and consistent across 37 files. The refactor only renames a parameter without changing any business logic, validation, or database queries. The parameter was already being used to query the slug field in the database, so the rename improves API naming clarity. Error messages were appropriately updated to reflect the new terminology.
• No files require special attention - all changes follow the same straightforward pattern

Important Files Changed