Skip to content

Restore old blocking access section and enhance

Tristan requested to merge docs-saml-blocking-access into master

What does this MR do?

This MR makes a few minor changes to the documentation for SAML SSO and SCIM Provisioning, primarily to revert a few changes made in a previous issue, linked below. In that issue a change was made that refers users reading the SAML SSO documentation to the SCIM documentation to learn how to block user access, but this does not account for users who are only using SAML SSO without SCIM.

It also corrects a section on the SCIM provisioning page regarding when an identity provider sync is made after making a change to the user to be more general, as all identity providers perform syncs at different intervals.

Related issues

Author's checklist

If you are only adding documentation, do not add any of the following labels:

  • ~"frontend"
  • ~"backend"
  • ~"type::bug"
  • ~"database"

These labels cause the MR to be added to code verification QA issues.

Review checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

  • If the content requires it, ensure the information is reviewed by a subject matter expert.
  • Technical writer review items:
    • Ensure docs metadata is present and up-to-date.
    • Ensure the appropriate labels are added to this MR.
    • If relevant to this MR, ensure content topic type principles are in use, including:
      • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
      • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
      • Any task steps should be written as a numbered list.
      • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
  • Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.
  • Ensure a release milestone is set.
Edited by Tristan

Merge request reports