QUA-1806: Correct SAML provider setup instructions#1126
Conversation
- Move Entity ID out of the "send" table. It is the Service Provider identifier that Qualytics generates, not something the customer sends. - Add a "Qualytics will then provide" table listing Entity ID and the Assertion Consumer Service (ACS) URL. Both are generated by Qualytics for the customer to configure on their IdP. - Mark "IdP metadata URL or XML" as optional and clarify it can be used instead of providing the Sign-in URL and Signing certificate separately.
Greptile SummaryThis PR corrects the SAML provider setup instructions in the SSO overview guide, fixing a factual error where Entity ID was incorrectly listed as something the customer sends to Qualytics (it is actually a Service Provider identifier that Qualytics generates and shares back).
Confidence Score: 5/5Documentation-only change that corrects a factual error in the SAML setup guide; no code paths are affected. The diff is a targeted documentation correction in a single markdown file. The reorganization of the SAML tables matches the stated intent from engineering: Entity ID moves to the SP-provided section, ACS URL is added, and the metadata row is clarified as optional. The resulting tables are internally consistent and the prose flows correctly. No files require special attention. Important Files Changed
Reviews (1): Last reviewed commit: "docs(sso): correct SAML setup value exch..." | Re-trigger Greptile |
Overview
Corrects the SAML provider section of the Single Sign-On setup guide. Engineering (Eric) flagged that the previous instructions listed Entity ID as something the customer sends to Qualytics, but it is actually a Service Provider identifier that Qualytics generates and provides back to the customer. The Assertion Consumer Service (ACS) URL was also missing from the values Qualytics shares.
Key Changes
Pages to Test
Screenshots