Due to the growth of new clients, the need for proper validation of profile names appeared. This ADR proposes adding new restrictions to profile names, which include length and special characters validations.
Profile entities currently have no requirements for their names beside being defined. This has caused different clients to allow the deployment of names with different criteria, resulting in naming inconsistencies. The aim of this ADR is to address this issue, standardizing the rules for names validation.
After the implementation of this ADR, names MUST:
To be more explicit about the new restrictions, names MUST now comply with the following JS Regex:
;/^[a-zA-Z0-9]{2,15}$/
This specification impacts:
Clients and sites deploying profile entities MUST include these validations before the deployment process of profiles. These clients MUST be aware of old profiles that, when being updated, MUST correct or prompt user for a new name or they will be rejected.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 and RFC 8174.