docs: rewrite Okta SCIM guide to meet OIN submission requirements

[michaelmmc]

Summary

Rewrites the "Provision with Okta" page (/fundamentals/account/account-security/scim-setup/okta/) to align with Okta's OIN configuration guide guidelines. This is required as part of the Cloudflare Dashboard SCIM OIN app submission process.

What changed

The existing page was a brief 3-section setup guide that referenced the generic "SCIM 2.0 Test App (OAuth Bearer Token)" rather than the published Cloudflare Dashboard OIN app. Okta's OIN review team provided specific feedback requiring a more complete guide. This PR addresses all of their feedback:

• Prerequisites — now includes explicit steps for retrieving the Cloudflare Account ID and creating a SCIM API token, which Okta flagged as missing
• Supported Features — new section with a table covering every Okta provisioning feature (including Import New Users and Import Profile Updates, which Okta noted were absent)
• Default Attributes — new section listing all accepted SCIM user attributes
• Configuration Steps — rewritten as 7 clear steps referencing the published OIN app, including the Sign On tab username format setting Okta requested
• Group Push — new dedicated section explaining how Group Push works, the dual-assignment requirement, naming restrictions, empty-group behavior, SCIM locking, and migration from legacy virtual groups
• Troubleshoot — new section covering unsupported attribute updates, permission gaps, Super Admin guardrails, 401 errors, and where to find logs
• Support — new section with support contact link

Context

This update is part of the Cloudflare Dashboard SCIM app submission to the Okta Integration Network (OIN). The OIN review team provided feedback in Item #2 of the submission that the existing configuration guide did not meet their documentation guidelines. Specifically, they required:

1. Reference to the published OIN app (not the test app)
2. How to fetch account_id after clicking Add Integration
3. Sections for Prerequisites, Supported Features, Configuration Steps, and Troubleshoot
4. List of default supported attributes
5. Explicit coverage of Import New Users / Import Profile Updates
6. Application username format guidance
7. A dedicated Group Push section
8. A customer support contact

All points are addressed in this rewrite.

[github-actions]

Hey there, we've marked this pull request as stale because there's no recent activity on it. This label helps us identify PRs that might need updates (or to be closed out by our team if no longer relevant).

[github-actions]

Hey there, we've closed out this pull request because it's been stale for a while and there's been no additional action on it. If these changes are still relevant, open a new pull request (or flag to us in a GitHub issue).