Back to catalog
Static reviewDevelopment

Skill dossier

implementing-scim-provisioning-with-okta

Source declaration

Implement automated user lifecycle provisioning and deprovisioning using the SCIM 2.0 protocol with Okta as the identity provider. Use when automating account creation, attribute sync, or deactivation across downstream applications through Okta SCIM integration, or when troubleshooting SCIM provisioning failures.

The author's original description, preserved in English. It describes intent, not verified performance.

Implement automated user lifecycle provisioning and deprovisioning using the SCIM 2.0 protocol with Okta as the identity provider. Use when automating account creation, attribute sync, or deactivation across downstream applications through Okta SCIM integration, or when troubleshooting SCIM provisioning failures.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Implement automated user lifecycle provisioning and deprovisioning using the SCIM 2.0 protocol with Okta as the identity provider. Use when automating account creation, attribute sync, or deactivation across downstream applications through Okta SCIM integration, or when troubleshooting SCIM provisioning failures. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/implementing-scim-provisioning-with-okta/SKILL.md:L116]
  • Step 1: Build SCIM 2.0 API Server [Source statement; provisional, not tested. Evidence: skills/implementing-scim-provisioning-with-okta/SKILL.md:L118]
  • Step 2: Configure Okta Application [Source statement; provisional, not tested. Evidence: skills/implementing-scim-provisioning-with-okta/SKILL.md:L185]
  • Step 3: Map Attributes [Source statement; provisional, not tested. Evidence: skills/implementing-scim-provisioning-with-okta/SKILL.md:L202]
  • Step 4: Implement Error Handling [Source statement; provisional, not tested. Evidence: skills/implementing-scim-provisioning-with-okta/SKILL.md:L214]
  • Step 5: Test with Runscope/Okta SCIM Validator [Source statement; provisional, not tested. Evidence: skills/implementing-scim-provisioning-with-okta/SKILL.md:L229]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/implementing-scim-provisioning-with-okta/SKILL.md:L1-L57]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
8
Markdown files
5
scripts
2
references
4
Size
56.5 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/implementing-scim-provisioning-with-okta/assets/template.mdReference2.5 KB
skills/implementing-scim-provisioning-with-okta/LICENSEOther11 KB
skills/implementing-scim-provisioning-with-okta/references/api-reference.mdReference4.6 KB
skills/implementing-scim-provisioning-with-okta/references/standards.mdReference2.3 KB
skills/implementing-scim-provisioning-with-okta/references/workflows.mdReference2.8 KB
skills/implementing-scim-provisioning-with-okta/scripts/agent.pyScript9 KB
skills/implementing-scim-provisioning-with-okta/scripts/process.pyScript15.3 KB
skills/implementing-scim-provisioning-with-okta/SKILL.mdInstruction9 KB

SKILL.md frontmatter

{
  "name": "implementing-scim-provisioning-with-okta",
  "description": "Implement automated user lifecycle provisioning and deprovisioning using the SCIM 2.0 protocol with Okta as the identity provider. Use when automating account creation, attribute sync, or deactivation across downstream applications through Okta SCIM integration, or when troubleshooting SCIM provisioning failures.",
  "domain": "cybersecurity",
  "subdomain": "identity-access-management",
  "tags": [
    "scim",
    "okta",
    "provisioning",
    "identity-management",
    "automation",
    "sso",
    "lifecycle-management"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.AA-01",
    "PR.AA-02",
    "PR.AA-05",
    "PR.AA-06"
  ],
  "mitre_attack": [
    "T1078",
    "T1110",
    "T1556",
    "T1098"
  ],
  "mitre_f3": {
    "version": "1.1",
    "tactics": [
      "initial-access",
      "positioning",
      "resource-development"
    ],
    "techniques": [
      {
        "id": "T1586",
        "name": "Compromise Accounts",
        "tactic": "resource-development",
        "source": "attack"
      },
      {
        "id": "F1005.002",
        "name": "Account Manipulation: Add Authorized User",
        "tactic": "positioning",
        "source": "f3"
      },
      {
        "id": "F1005.004",
        "name": "Account Manipulation: Change Account Details",
        "tactic": "positioning",
        "source": "f3"
      },
      {
        "id": "F1042",
        "name": "Reactivate Account",
        "tactic": "positioning",
        "source": "f3"
      },
      {
        "id": "F1006.002",
        "name": "Account Takeover: Exposed Login Credential",
        "tactic": "initial-access",
        "source": "f3"
      }
    ]
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Action

    Overview

    Source-described action candidate under “Overview”; not verified execution.

  2. 02
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  3. 03
    Action

    Core Concepts

    Source-described action candidate under “Core Concepts”; not verified execution.

  4. 04
    Action

    ServiceProviderConfig (`/scim/v2/ServiceProviderConfig`): Advertises SCIM capabilities

    Source-described action candidate under “Required SCIM Endpoints”; not verified execution.

  5. 05
    Action

    ResourceTypes (`/scim/v2/ResourceTypes`): Describes supported resource types

    Source-described action candidate under “Required SCIM Endpoints”; not verified execution.

  6. 06
    Action

    Schemas (`/scim/v2/Schemas`): Publishes the SCIM schema definitions

    Source-described action candidate under “Required SCIM Endpoints”; not verified execution.

Inspect all extracted workflow candidates (37 candidate steps)
  1. 07
    Action

    Users (`/scim/v2/Users`): User lifecycle operations

    Source-described action candidate under “Required SCIM Endpoints”; not verified execution.

  2. 08
    Action

    Groups (`/scim/v2/Groups`): Group management operations

    Source-described action candidate under “Required SCIM Endpoints”; not verified execution.

  3. 09
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  4. 10
    Action

    Step 1: Build SCIM 2.0 API Server

    Source-described action candidate under “Step 1: Build SCIM 2.0 API Server”; not verified execution.

  5. 11
    Action

    Create a Flask-based SCIM server that implements the core endpoints. The server must handle:

    Source-described action candidate under “Step 1: Build SCIM 2.0 API Server”; not verified execution.

  6. 12
    Input

    User CRUD: Create, read, update, delete, and list users

    Source-described input candidate under “Step 1: Build SCIM 2.0 API Server”; not verified execution.

  7. 13
    Action

    Filtering: Support `eq` filter on `userName` (required by Okta)

    Source-described action candidate under “Step 1: Build SCIM 2.0 API Server”; not verified execution.

  8. 14
    Output

    Pagination: Return `startIndex`, `itemsPerPage`, and `totalResults`

    Source-described output candidate under “Step 1: Build SCIM 2.0 API Server”; not verified execution.

  9. 15
    Action

    Authentication: Bearer token validation on all endpoints

    Source-described action candidate under “Step 1: Build SCIM 2.0 API Server”; not verified execution.

  10. 16
    Action

    Step 2: Configure Okta Application

    Source-described action candidate under “Step 2: Configure Okta Application”; not verified execution.

  11. 17
    Action

    Create SCIM App Integration:

    Source-described action candidate under “Step 2: Configure Okta Application”; not verified execution.

  12. 18
    Action

    Navigate to Okta Admin Console > Applications > Create App Integration

    Source-described action candidate under “Step 2: Configure Okta Application”; not verified execution.

  13. 19
    Action

    Select SWA or SAML 2.0 as sign-on method

    Source-described action candidate under “Step 2: Configure Okta Application”; not verified execution.

  14. 20
    Action

    In the General tab, select SCIM for Provisioning

    Source-described action candidate under “Step 2: Configure Okta Application”; not verified execution.

  15. 21
    Action

    Configure SCIM Connection:

    Source-described action candidate under “Step 2: Configure Okta Application”; not verified execution.

  16. 22
    Action

    SCIM connector base URL: `https://your-app.com/scim/v2`

    Source-described action candidate under “Step 2: Configure Okta Application”; not verified execution.

  17. 23
    Action

    Unique identifier field: `userName`

    Source-described action candidate under “Step 2: Configure Okta Application”; not verified execution.

  18. 24
    Action

    Supported provisioning actions: Push New Users, Push Profile Updates, Push Groups

    Source-described action candidate under “Step 2: Configure Okta Application”; not verified execution.

  19. 25
    Action

    Authentication Mode: HTTP Header (Bearer Token)

    Source-described action candidate under “Step 2: Configure Okta Application”; not verified execution.

  20. 26
    Action

    Enable Provisioning Features:

    Source-described action candidate under “Step 2: Configure Okta Application”; not verified execution.

  21. 27
    Action

    To App: Create Users, Update User Attributes, Deactivate Users

    Source-described action candidate under “Step 2: Configure Okta Application”; not verified execution.

  22. 28
    Action

    Configure attribute mappings between Okta profile and SCIM schema

    Source-described action candidate under “Step 2: Configure Okta Application”; not verified execution.

  23. 29
    Action

    Step 3: Map Attributes

    Source-described action candidate under “Step 3: Map Attributes”; not verified execution.

  24. 30
    Action

    Step 4: Implement Error Handling

    Source-described action candidate under “Step 4: Implement Error Handling”; not verified execution.

  25. 31
    Action

    Step 5: Test with Runscope/Okta SCIM Validator

    Source-described action candidate under “Step 5: Test with Runscope/Okta SCIM Validator”; not verified execution.

  26. 32
    Input

    Import the Okta SCIM 2.0 test suite from the OIN submission portal

    Source-described input candidate under “Step 5: Test with Runscope/Okta SCIM Validator”; not verified execution.

  27. 33
    Action

    Configure the base URL and authentication token

    Source-described action candidate under “Step 5: Test with Runscope/Okta SCIM Validator”; not verified execution.

  28. 34
    Action

    Run the full test suite covering user CRUD, filtering, and pagination

    Source-described action candidate under “Step 5: Test with Runscope/Okta SCIM Validator”; not verified execution.

  29. 35
    Action

    Fix any failing tests before submitting to OIN

    Source-described action candidate under “Step 5: Test with Runscope/Okta SCIM Validator”; not verified execution.

  30. 36
    Action

    Validation Checklist

    Source-described action candidate under “Validation Checklist”; not verified execution.

  31. 37
    Action

    References

    Source-described action candidate under “References”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

39 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Medium

Network access is mentioned

19 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 19 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

19 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 19 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/implementing-scim-provisioning-with-okta/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/implementing-scim-provisioning-with-okta/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/implementing-scim-provisioning-with-okta
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.