RELEASED: Public: April 2, 2025
Resolved issues
- User properties now propagate upon successful sign in with an API token (BEE-48018)
-
User properties were propagated from the operations center to controllers when signing in with a username and password using SSH. However, this did not occur when interacting with controllers that used a username and an API token. Therefore, for non-interactive users (for example, service accounts) that only called the Jenkins API using API tokens, if the operations center was unavailable, these service accounts could no longer sign in to controllers. This issue has been resolved, so user data propagation is now also performed when using API tokens.