Back to catalog
Static reviewDevelopment

Skill dossier

implementing-saml-sso-with-okta

Source declaration

Implement SAML 2.0 Single Sign-On using Okta as the Identity Provider, covering SP-initiated and IdP-initiated flows, attribute mapping, certificate management, SHA-256 signature enforcement, and Single Logout. Use when configuring Okta SAML SSO for an application, hardening SAML certificate rotation and signing, or testing and troubleshooting SAML assertion flows with a tracer tool.

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

Implement SAML 2.0 Single Sign-On using Okta as the Identity Provider, covering SP-initiated and IdP-initiated flows, attribute mapping, certificate management, SHA-256 signature enforcement, and Single Logout. Use when configuring Okta SAML SSO for an application, hardening SAML certificate rotation and signing, or testing and troubleshooting SAML assertion flows with a tracer tool.

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 SAML 2.0 Single Sign-On using Okta as the Identity Provider, covering SP-initiated and IdP-initiated flows, attribute mapping, certificate management, SHA-256 signature enforcement, and Single Logout. Use when configuring Okta SAML SSO for an application, hardening SAML certificate rotation and signing, or testing and troubleshooting SAML assertion flows with a tracer tool. 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-saml-sso-with-okta/SKILL.md:L108]
  • Step 1: Create SAML Application in Okta [Source statement; provisional, not tested. Evidence: skills/implementing-saml-sso-with-okta/SKILL.md:L110]
  • Step 2: Configure Attribute Mapping [Source statement; provisional, not tested. Evidence: skills/implementing-saml-sso-with-okta/SKILL.md:L118]
  • Step 3: Download and Install IdP Metadata [Source statement; provisional, not tested. Evidence: skills/implementing-saml-sso-with-okta/SKILL.md:L124]
  • Step 4: Implement SP-Side SAML Processing [Source statement; provisional, not tested. Evidence: skills/implementing-saml-sso-with-okta/SKILL.md:L130]
  • Step 5: Security Hardening [Source statement; provisional, not tested. Evidence: skills/implementing-saml-sso-with-okta/SKILL.md:L137]
  • Step 6: Testing and Validation [Source statement; provisional, not tested. Evidence: skills/implementing-saml-sso-with-okta/SKILL.md:L144]

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-saml-sso-with-okta/SKILL.md:L1-L59]

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
55.8 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/implementing-saml-sso-with-okta/assets/template.mdReference4.1 KB
skills/implementing-saml-sso-with-okta/LICENSEOther11 KB
skills/implementing-saml-sso-with-okta/references/api-reference.mdReference1.6 KB
skills/implementing-saml-sso-with-okta/references/standards.mdReference2.1 KB
skills/implementing-saml-sso-with-okta/references/workflows.mdReference3.4 KB
skills/implementing-saml-sso-with-okta/scripts/agent.pyScript7.6 KB
skills/implementing-saml-sso-with-okta/scripts/process.pyScript19.2 KB
skills/implementing-saml-sso-with-okta/SKILL.mdInstruction6.6 KB

SKILL.md frontmatter

{
  "name": "implementing-saml-sso-with-okta",
  "description": "Implement SAML 2.0 Single Sign-On using Okta as the Identity Provider, covering SP-initiated and IdP-initiated flows, attribute mapping, certificate management, SHA-256 signature enforcement, and Single Logout. Use when configuring Okta SAML SSO for an application, hardening SAML certificate rotation and signing, or testing and troubleshooting SAML assertion flows with a tracer tool.",
  "domain": "cybersecurity",
  "subdomain": "identity-access-management",
  "tags": [
    "iam",
    "identity",
    "access-control",
    "authentication",
    "saml",
    "sso",
    "okta"
  ],
  "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",
    "T1553"
  ],
  "mitre_f3": {
    "version": "1.1",
    "tactics": [
      "initial-access",
      "positioning",
      "resource-development"
    ],
    "techniques": [
      {
        "id": "T1586",
        "name": "Compromise Accounts",
        "tactic": "resource-development",
        "source": "attack"
      },
      {
        "id": "T1539",
        "name": "Steal Web Session Cookie",
        "tactic": "positioning",
        "source": "attack"
      },
      {
        "id": "F1004",
        "name": "Access with Stolen Session Cookie",
        "tactic": "initial-access",
        "source": "f3"
      },
      {
        "id": "T1550.001",
        "name": "Use Alternate Authentication Material: Application Access Token",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "F1006.003",
        "name": "Account Takeover: Password Reset",
        "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

    Objectives

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

  4. 04
    Action

    Key Concepts

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

  5. 05
    Action

    SP-Initiated Flow: User accesses Service Provider -> SP generates AuthnRequest -> Redirect to Okta IdP -> User authenticates -> Okta sends SAML Response -> SP validates assertion -> Access granted

    Source-described action candidate under “SAML 2.0 Authentication Flow”; not verified execution.

  6. 06
    Action

    IdP-Initiated Flow: User authenticates at Okta -> Selects application -> Okta sends unsolicited SAML Response -> SP validates -> Access granted

    Source-described action candidate under “SAML 2.0 Authentication Flow”; not verified execution.

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

    Workflow

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

  2. 08
    Action

    Step 1: Create SAML Application in Okta

    Source-described action candidate under “Step 1: Create SAML Application in Okta”; not verified execution.

  3. 09
    Action

    Navigate to Applications > Create App Integration

    Source-described action candidate under “Step 1: Create SAML Application in Okta”; not verified execution.

  4. 10
    Action

    Select SAML 2.0 as the sign-on method

    Source-described action candidate under “Step 1: Create SAML Application in Okta”; not verified execution.

  5. 11
    Action

    Configure General Settings (App Name, Logo)

    Source-described action candidate under “Step 1: Create SAML Application in Okta”; not verified execution.

  6. 12
    Action

    Set Single Sign-On URL (ACS URL)

    Source-described action candidate under “Step 1: Create SAML Application in Okta”; not verified execution.

  7. 13
    Action

    Set Audience URI (SP Entity ID)

    Source-described action candidate under “Step 1: Create SAML Application in Okta”; not verified execution.

  8. 14
    Action

    Configure Name ID Format and Application Username

    Source-described action candidate under “Step 1: Create SAML Application in Okta”; not verified execution.

  9. 15
    Action

    Step 2: Configure Attribute Mapping

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

  10. 16
    Action

    Map `user.email` to `email` attribute

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

  11. 17
    Action

    Map `user.firstName` and `user.lastName` to name attributes

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

  12. 18
    Action

    Add group attribute statements for role-based access

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

  13. 19
    Action

    Configure attribute value formats (Basic, URI Reference, Unspecified)

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

  14. 20
    Action

    Step 3: Download and Install IdP Metadata

    Source-described action candidate under “Step 3: Download and Install IdP Metadata”; not verified execution.

  15. 21
    Action

    Download Okta IdP metadata XML

    Source-described action candidate under “Step 3: Download and Install IdP Metadata”; not verified execution.

  16. 22
    Action

    Extract IdP SSO URL, IdP Entity ID, and X.509 certificate

    Source-described action candidate under “Step 3: Download and Install IdP Metadata”; not verified execution.

  17. 23
    Action

    Install certificate on SP side for signature validation

    Source-described action candidate under “Step 3: Download and Install IdP Metadata”; not verified execution.

  18. 24
    Action

    Configure SP metadata with ACS URL and Entity ID

    Source-described action candidate under “Step 3: Download and Install IdP Metadata”; not verified execution.

  19. 25
    Action

    Step 4: Implement SP-Side SAML Processing

    Source-described action candidate under “Step 4: Implement SP-Side SAML Processing”; not verified execution.

  20. 26
    Action

    Parse and validate SAML Response XML

    Source-described action candidate under “Step 4: Implement SP-Side SAML Processing”; not verified execution.

  21. 27
    Action

    Verify digital signature using IdP certificate

    Source-described action candidate under “Step 4: Implement SP-Side SAML Processing”; not verified execution.

  22. 28
    Action

    Check audience restriction, time conditions, and InResponseTo

    Source-described action candidate under “Step 4: Implement SP-Side SAML Processing”; not verified execution.

  23. 29
    Action

    Extract authenticated user identity and attributes

    Source-described action candidate under “Step 4: Implement SP-Side SAML Processing”; not verified execution.

  24. 30
    Action

    Create application session based on assertion data

    Source-described action candidate under “Step 4: Implement SP-Side SAML Processing”; not verified execution.

  25. 31
    Action

    Step 5: Security Hardening

    Source-described action candidate under “Step 5: Security Hardening”; not verified execution.

  26. 32
    Action

    Enforce SHA-256 for all signature operations

    Source-described action candidate under “Step 5: Security Hardening”; not verified execution.

  27. 33
    Action

    Enable assertion encryption with AES-256-CBC

    Source-described action candidate under “Step 5: Security Hardening”; not verified execution.

  28. 34
    Action

    Configure session timeout and re-authentication policies

    Source-described action candidate under “Step 5: Security Hardening”; not verified execution.

  29. 35
    Action

    Implement SAML artifact binding for sensitive deployments

    Source-described action candidate under “Step 5: Security Hardening”; not verified execution.

  30. 36
    Action

    Set up certificate rotation procedure before expiry

    Source-described action candidate under “Step 5: Security Hardening”; not verified execution.

  31. 37
    Action

    Step 6: Testing and Validation

    Source-described action candidate under “Step 6: Testing and Validation”; not verified execution.

  32. 38
    Action

    Use SAML Tracer browser extension for debugging

    Source-described action candidate under “Step 6: Testing and Validation”; not verified execution.

  33. 39
    Action

    Validate SP-initiated and IdP-initiated flows

    Source-described action candidate under “Step 6: Testing and Validation”; not verified execution.

  34. 40
    Action

    Test with multiple user accounts and group memberships

    Source-described action candidate under “Step 6: Testing and Validation”; not verified execution.

  35. 41
    Action

    Verify SLO functionality

    Source-described action candidate under “Step 6: Testing and Validation”; not verified execution.

  36. 42
    Action

    Test certificate rotation without downtime

    Source-described action candidate under “Step 6: Testing and Validation”; not verified execution.

  37. 43
    Action

    Security Controls

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

  38. 44
    Action

    Common Pitfalls

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

  39. 45
    Action

    Verification

    Source-described action candidate under “Verification”; 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.

Items warrant review

61 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 useNot observed
Note

File modification is described or implemented

20 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 20 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

41 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 41 location(s) in the collected text; 3 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-saml-sso-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-saml-sso-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-saml-sso-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.