[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMQKT723Y12WJAXT4REM43":3,"skill-same:01M7EMQKT723Y12WJAXT4REM43":107},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":71,"commitSha":72,"skillDirectory":73,"forksCount":74,"repositoryHtmlUrl":75,"repositoryHomepageUrl":6,"ownerHtmlUrl":76,"ownerBlogUrl":6,"ownerDescription":77,"updatedAt":78,"install":79,"resources":92},"01M7EMQKT723Y12WJAXT4REM43","implementing-saml-sso-with-okta",null,"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.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fimplementing-saml-sso-with-okta\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implementing-saml-sso-with-okta\ndescription: Implement SAML 2.0 Single Sign-On using Okta as the Identity Provider,\n  covering SP-initiated and IdP-initiated flows, attribute mapping, certificate management,\n  SHA-256 signature enforcement, and Single Logout. Use when configuring Okta SAML SSO\n  for an application, hardening SAML certificate rotation and signing, or testing and\n  troubleshooting SAML assertion flows with a tracer tool.\ndomain: cybersecurity\nsubdomain: identity-access-management\ntags:\n- iam\n- identity\n- access-control\n- authentication\n- saml\n- sso\n- okta\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.AA-01\n- PR.AA-02\n- PR.AA-05\n- PR.AA-06\nmitre_attack:\n- T1078\n- T1110\n- T1556\n- T1098\n- T1553\nmitre_f3:\n  version: '1.1'\n  tactics:\n  - initial-access\n  - positioning\n  - resource-development\n  techniques:\n  - id: T1586\n    name: Compromise Accounts\n    tactic: resource-development\n    source: attack\n  - id: T1539\n    name: Steal Web Session Cookie\n    tactic: positioning\n    source: attack\n  - id: F1004\n    name: Access with Stolen Session Cookie\n    tactic: initial-access\n    source: f3\n  - id: T1550.001\n    name: 'Use Alternate Authentication Material: Application Access Token'\n    tactic: initial-access\n    source: attack\n  - id: F1006.003\n    name: 'Account Takeover: Password Reset'\n    tactic: initial-access\n    source: f3\n---\n# Implementing SAML SSO with Okta\n\n## Overview\nImplement SAML 2.0 Single Sign-On (SSO) using Okta as the Identity Provider (IdP). This skill covers end-to-end configuration of SAML authentication flows, attribute mapping, certificate management, and security hardening for enterprise SSO deployments.\n\n\n## When to Use\n\n- When deploying or configuring implementing saml sso with okta capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Familiarity with identity access management concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n- Configure Okta as a SAML 2.0 Identity Provider\n- Implement SP-initiated and IdP-initiated SSO flows\n- Map SAML attributes and configure assertion encryption\n- Enforce SHA-256 signatures and secure certificate rotation\n- Test SSO flows with SAML tracer tools\n- Implement Single Logout (SLO) handling\n\n## Key Concepts\n\n### SAML 2.0 Authentication Flow\n1. **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\n2. **IdP-Initiated Flow**: User authenticates at Okta -> Selects application -> Okta sends unsolicited SAML Response -> SP validates -> Access granted\n\n### Critical Security Requirements\n- **SHA-256 Signatures**: All SAML assertions must use SHA-256 (not SHA-1) for digital signatures\n- **Assertion Encryption**: Encrypt SAML assertions using AES-256 to protect attribute values in transit\n- **Audience Restriction**: Configure audience URI to prevent assertion replay across different SPs\n- **NotBefore\u002FNotOnOrAfter**: Enforce time validity windows to prevent stale assertion usage\n- **InResponseTo Validation**: Verify assertion corresponds to the original AuthnRequest\n\n### Okta Application Configuration\n- **Single Sign-On URL**: The ACS (Assertion Consumer Service) endpoint on the SP\n- **Audience URI (SP Entity ID)**: Unique identifier for the SP\n- **Name ID Format**: EmailAddress, Persistent, or Transient\n- **Attribute Statements**: Map Okta user profile attributes to SAML assertion attributes\n- **Group Attribute Statements**: Include group membership for RBAC\n\n## Workflow\n\n### Step 1: Create SAML Application in Okta\n1. Navigate to Applications > Create App Integration\n2. Select SAML 2.0 as the sign-on method\n3. Configure General Settings (App Name, Logo)\n4. Set Single Sign-On URL (ACS URL)\n5. Set Audience URI (SP Entity ID)\n6. Configure Name ID Format and Application Username\n\n### Step 2: Configure Attribute Mapping\n- Map `user.email` to `email` attribute\n- Map `user.firstName` and `user.lastName` to name attributes\n- Add group attribute statements for role-based access\n- Configure attribute value formats (Basic, URI Reference, Unspecified)\n\n### Step 3: Download and Install IdP Metadata\n- Download Okta IdP metadata XML\n- Extract IdP SSO URL, IdP Entity ID, and X.509 certificate\n- Install certificate on SP side for signature validation\n- Configure SP metadata with ACS URL and Entity ID\n\n### Step 4: Implement SP-Side SAML Processing\n- Parse and validate SAML Response XML\n- Verify digital signature using IdP certificate\n- Check audience restriction, time conditions, and InResponseTo\n- Extract authenticated user identity and attributes\n- Create application session based on assertion data\n\n### Step 5: Security Hardening\n- Enforce SHA-256 for all signature operations\n- Enable assertion encryption with AES-256-CBC\n- Configure session timeout and re-authentication policies\n- Implement SAML artifact binding for sensitive deployments\n- Set up certificate rotation procedure before expiry\n\n### Step 6: Testing and Validation\n- Use SAML Tracer browser extension for debugging\n- Validate SP-initiated and IdP-initiated flows\n- Test with multiple user accounts and group memberships\n- Verify SLO functionality\n- Test certificate rotation without downtime\n\n## Security Controls\n| Control | NIST 800-53 | Description |\n|---------|-------------|-------------|\n| Authentication | IA-2 | Multi-factor authentication through Okta |\n| Session Management | SC-23 | SAML session lifetime controls |\n| Audit Logging | AU-3 | Log all SSO authentication events |\n| Certificate Management | SC-17 | PKI certificate lifecycle management |\n| Access Enforcement | AC-3 | SAML attribute-based access control |\n\n## Common Pitfalls\n- Using SHA-1 instead of SHA-256 for SAML signatures\n- Not validating InResponseTo in SAML responses (replay attacks)\n- Clock skew between IdP and SP causing assertion rejection\n- Failing to restrict audience URI allowing assertion forwarding\n- Not implementing certificate rotation before expiry causes outage\n\n## Verification\n- [ ] SAML SSO login completes successfully via SP-initiated flow\n- [ ] IdP-initiated flow correctly authenticates users\n- [ ] SAML assertions use SHA-256 signatures\n- [ ] Attribute mapping correctly populates user profile\n- [ ] Session timeout forces re-authentication\n- [ ] SLO properly terminates sessions on both IdP and SP\n- [ ] Certificate rotation tested without service interruption\n","# Implementing SAML SSO with Okta\n\n## Overview\nImplement SAML 2.0 Single Sign-On (SSO) using Okta as the Identity Provider (IdP). This skill covers end-to-end configuration of SAML authentication flows, attribute mapping, certificate management, and security hardening for enterprise SSO deployments.\n\n\n## When to Use\n\n- When deploying or configuring implementing saml sso with okta capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Familiarity with identity access management concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n- Configure Okta as a SAML 2.0 Identity Provider\n- Implement SP-initiated and IdP-initiated SSO flows\n- Map SAML attributes and configure assertion encryption\n- Enforce SHA-256 signatures and secure certificate rotation\n- Test SSO flows with SAML tracer tools\n- Implement Single Logout (SLO) handling\n\n## Key Concepts\n\n### SAML 2.0 Authentication Flow\n1. **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\n2. **IdP-Initiated Flow**: User authenticates at Okta -> Selects application -> Okta sends unsolicited SAML Response -> SP validates -> Access granted\n\n### Critical Security Requirements\n- **SHA-256 Signatures**: All SAML assertions must use SHA-256 (not SHA-1) for digital signatures\n- **Assertion Encryption**: Encrypt SAML assertions using AES-256 to protect attribute values in transit\n- **Audience Restriction**: Configure audience URI to prevent assertion replay across different SPs\n- **NotBefore\u002FNotOnOrAfter**: Enforce time validity windows to prevent stale assertion usage\n- **InResponseTo Validation**: Verify assertion corresponds to the original AuthnRequest\n\n### Okta Application Configuration\n- **Single Sign-On URL**: The ACS (Assertion Consumer Service) endpoint on the SP\n- **Audience URI (SP Entity ID)**: Unique identifier for the SP\n- **Name ID Format**: EmailAddress, Persistent, or Transient\n- **Attribute Statements**: Map Okta user profile attributes to SAML assertion attributes\n- **Group Attribute Statements**: Include group membership for RBAC\n\n## Workflow\n\n### Step 1: Create SAML Application in Okta\n1. Navigate to Applications > Create App Integration\n2. Select SAML 2.0 as the sign-on method\n3. Configure General Settings (App Name, Logo)\n4. Set Single Sign-On URL (ACS URL)\n5. Set Audience URI (SP Entity ID)\n6. Configure Name ID Format and Application Username\n\n### Step 2: Configure Attribute Mapping\n- Map `user.email` to `email` attribute\n- Map `user.firstName` and `user.lastName` to name attributes\n- Add group attribute statements for role-based access\n- Configure attribute value formats (Basic, URI Reference, Unspecified)\n\n### Step 3: Download and Install IdP Metadata\n- Download Okta IdP metadata XML\n- Extract IdP SSO URL, IdP Entity ID, and X.509 certificate\n- Install certificate on SP side for signature validation\n- Configure SP metadata with ACS URL and Entity ID\n\n### Step 4: Implement SP-Side SAML Processing\n- Parse and validate SAML Response XML\n- Verify digital signature using IdP certificate\n- Check audience restriction, time conditions, and InResponseTo\n- Extract authenticated user identity and attributes\n- Create application session based on assertion data\n\n### Step 5: Security Hardening\n- Enforce SHA-256 for all signature operations\n- Enable assertion encryption with AES-256-CBC\n- Configure session timeout and re-authentication policies\n- Implement SAML artifact binding for sensitive deployments\n- Set up certificate rotation procedure before expiry\n\n### Step 6: Testing and Validation\n- Use SAML Tracer browser extension for debugging\n- Validate SP-initiated and IdP-initiated flows\n- Test with multiple user accounts and group memberships\n- Verify SLO functionality\n- Test certificate rotation without downtime\n\n## Security Controls\n| Control | NIST 800-53 | Description |\n|---------|-------------|-------------|\n| Authentication | IA-2 | Multi-factor authentication through Okta |\n| Session Management | SC-23 | SAML session lifetime controls |\n| Audit Logging | AU-3 | Log all SSO authentication events |\n| Certificate Management | SC-17 | PKI certificate lifecycle management |\n| Access Enforcement | AC-3 | SAML attribute-based access control |\n\n## Common Pitfalls\n- Using SHA-1 instead of SHA-256 for SAML signatures\n- Not validating InResponseTo in SAML responses (replay attacks)\n- Clock skew between IdP and SP causing assertion rejection\n- Failing to restrict audience URI allowing assertion forwarding\n- Not implementing certificate rotation before expiry causes outage\n\n## Verification\n- [ ] SAML SSO login completes successfully via SP-initiated flow\n- [ ] IdP-initiated flow correctly authenticates users\n- [ ] SAML assertions use SHA-256 signatures\n- [ ] Attribute mapping correctly populates user profile\n- [ ] Session timeout forces re-authentication\n- [ ] SLO properly terminates sessions on both IdP and SP\n- [ ] Certificate rotation tested without service interruption\n",{"name":5,"tags":24,"author":32,"domain":33,"license":15,"version":34,"mitre_f3":35,"nist_csf":59,"subdomain":64,"description":7,"mitre_attack":65},[25,26,27,28,29,30,31],"iam","identity","access-control","authentication","saml","sso","okta","mahipal","cybersecurity","1.0",{"tactics":36,"version":40,"techniques":41},[37,38,39],"initial-access","positioning","resource-development","1.1",[42,46,49,53,56],{"id":43,"name":44,"source":45,"tactic":39},"T1586","Compromise Accounts","attack",{"id":47,"name":48,"source":45,"tactic":38},"T1539","Steal Web Session Cookie",{"id":50,"name":51,"source":52,"tactic":37},"F1004","Access with Stolen Session Cookie","f3",{"id":54,"name":55,"source":45,"tactic":37},"T1550.001","Use Alternate Authentication Material: Application Access Token",{"id":57,"name":58,"source":52,"tactic":37},"F1006.003","Account Takeover: Password Reset",[60,61,62,63],"PR.AA-01","PR.AA-02","PR.AA-05","PR.AA-06","identity-access-management",[66,67,68,69,70],"T1078","T1110","T1556","T1098","T1553","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fimplementing-saml-sso-with-okta",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":80,"prompt":90,"zipAvailable":91},[81,84,87],{"tool":82,"command":83},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill implementing-saml-sso-with-okta",{"tool":85,"command":86},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill implementing-saml-sso-with-okta",{"tool":88,"command":89},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill implementing-saml-sso-with-okta","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fimplementing-saml-sso-with-okta\u002FSKILL.md",true,[93,99,103],{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fapi-reference.md","REFERENCE","参考文档",1663,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fimplementing-saml-sso-with-okta\u002Freferences\u002Fapi-reference.md",{"path":100,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fstandards.md",2170,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fimplementing-saml-sso-with-okta\u002Freferences\u002Fstandards.md",{"path":104,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fworkflows.md",3516,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fimplementing-saml-sso-with-okta\u002Freferences\u002Fworkflows.md",[108,117,122,129,136,143],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":112,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":116},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":118,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":112,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":116},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":112,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":116},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":112,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":116},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":112,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":116},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":112,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":116},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]