You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 30, 2024. It is now read-only.
We encountered an issue where usernames with suffixes are breaking permissions syncs with Bitbucket, as Bitbucket requires exact username matches. Sourcegraph normalizes usernames by adding a suffix if the username is in email format. This discrepancy affects setups where SCIM and SAML are involved and the username has to be set as an email.
Steps to reproduce:
Set up SCIM and SAML with Okta.
Create a user and sync permissions with Bitbucket.
Expected behavior:
Usernames should match exactly between Sourcegraph and Bitbucket without normalization issues.
Actual behavior:
Usernames in Sourcegraph get a suffix added during normalization, causing mismatches with Bitbucket usernames.
If you would like immediate help on this, please email support@sourcegraph.com (you can still create the issue, but there are no SLAs on issues like there are for support requests).
We encountered an issue where usernames with suffixes are breaking permissions syncs with Bitbucket, as Bitbucket requires exact username matches. Sourcegraph normalizes usernames by adding a suffix if the username is in email format. This discrepancy affects setups where SCIM and SAML are involved and the username has to be set as an email.
Steps to reproduce:
Expected behavior:
Usernames should match exactly between Sourcegraph and Bitbucket without normalization issues.
Actual behavior:
Usernames in Sourcegraph get a suffix added during normalization, causing mismatches with Bitbucket usernames.
If you would like immediate help on this, please email support@sourcegraph.com (you can still create the issue, but there are no SLAs on issues like there are for support requests).