User name stability

Problem

In the decision regarding User object names in the OpenShift cluster, we chose to use the user’s Keycloak Username property as the identifier for the user in the OpenShift cluster.

Due to some technical limitations in OpenShift, this choice requires that the user’s Username remains stable for the lifetime of the user.

Relevant decisions

Proposals

  1. Disallow Username changes

  2. Implement extra tooling to work around the limitations in OpenShift and allow Username changes.

Decision

Disallow Username changes

Rationale

We decide to disallow users to change their Username after creation of the user in APPUiO Cloud. If a user needs to change their Username, they can register a new user with the desired Username and add the new user to the appropriate organizations.