Support users with apostrophe in email
M
Mark Tarry
It is valid for a user to have an apostrophe in their email address. Email address seems to be the defacto value used as an
identifier
for the system-managed _user
blueprint.Example:
j.o'bloggs@ourdomain.com
Port does not appear to support such an email address.
If we attempt to create such a user via the web app:
> j.o'bloggs@ourdomain.com is not a valid email
If we attempt to upsert the entity via the Port APIs, the audit log shows an error:
> "identifier" must match pattern "^[A-Za-z0-9@_.+:\\/=-]+$"
E
Eamon Mason
Apostrophes are valid characters in email local parts according to RFC 3696 :
"In the context of local parts, apostrophe ("'") and acute accent ("`") are ordinary characters, not quoting characters."
A number of our employees have email addresses containing apostrophes prior to the @ symbol (e.g., surnames like O'Brien, O'Connor). These users cannot be provisioned in Port, creating:
- Incomplete user coverage — Affected employees cannot access the Internal Developer Portal
- Manual workarounds — Requires alternative identity management approaches
- Compliance gaps — User provisioning cannot be fully automated via SSO/SCIM