Improve troubleshooting process/knowledge on SAML SSO For Groups
Screenshots link: https://drive.google.com/drive/folders/103gAm1qmBlYwG6f-aT9thrNbcPRD1KH5
7/22/19 Update:
Azure seems to be both the most troublesome provider to configure SAML SSO and SCIM with and is also the one that we receive the most contact on so we're focusing our efforts on understanding it better first.
I've created a personal Azure account (on 30 day trial) and testing group to work with and earlier today @cynthia and I were able to get a base SSO configuration working. We identified the following items that would improve how we help customers with SAML issues in general and especially those using Azure.
- Create and maintain testing instances for each SAML provider (if feasible) that the support team can use for SAML testing and troubleshooting.
- Submit documentation MRs to improve our SAML SSO For Groups and SCIM specific documentation. Ideally, we should have a document for each provider that goes over the specifics and quirks of configuring each.
- Schedule a call internally with Manage requesting their assistance in troubleshooting SAML and SCIM issues that we're struggling with.
Original Description:
A feature we seem to struggle with a lot on the GitLab.com team is most issues surrounding SAML SSO For GitLab.com Groups. It feels like we don't know enough as a team about how to troubleshoot issues with the various providers that are supported by this feature.
What can we do to expand our knowledge and make tackling issues with this feature easier on both us and the customer? e.g. additions to documentation, test environments for each provider (if feasible), workflows, etc.
If any come to mind, let's link some difficult tickets here and see if there are any trends or common areas.
/cc @dotcom-support