[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EBTCG59EABY0893XT7KA5S":3,"skill-same:01M7EBTCG59EABY0893XT7KA5S":106},{"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":70,"commitSha":71,"skillDirectory":72,"forksCount":73,"repositoryHtmlUrl":74,"repositoryHomepageUrl":6,"ownerHtmlUrl":75,"ownerBlogUrl":6,"ownerDescription":76,"updatedAt":77,"install":78,"resources":91},"01M7EBTCG59EABY0893XT7KA5S","building-identity-federation-with-saml-azure-ad",null,"Configure SAML 2.0 identity federation between on-premises Active Directory (via AD FS or a third-party IdP) and Microsoft Entra ID, covering federation models (AD FS, password hash sync, pass-through auth, third-party IdP) and the SAML authentication flow. Use when extending on-premises authentication authority to cloud resources or designing hybrid identity SSO architecture for Entra ID.","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\u002F03-逆向工程\u002Fbuilding-identity-federation-with-saml-azure-ad\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: building-identity-federation-with-saml-azure-ad\ndescription: Configure SAML 2.0 identity federation between on-premises Active Directory (via AD FS or a third-party IdP) and Microsoft Entra ID, covering federation models (AD FS, password hash sync, pass-through auth, third-party IdP) and the SAML authentication flow. Use when extending on-premises authentication authority to cloud resources or designing hybrid identity SSO architecture for Entra ID.\ndomain: cybersecurity\nsubdomain: identity-access-management\ntags:\n- saml\n- azure-ad\n- entra-id\n- federation\n- identity\n- sso\n- adfs\n- hybrid-identity\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- T1606.002\n- T1556.007\n- T1484.002\n- T1078.004\n- T1110.003\nmitre_f3:\n  version: '1.1'\n  tactics:\n  - initial-access\n  - positioning\n  techniques:\n  - id: F1006\n    name: Account Takeover\n    tactic: initial-access\n    source: f3\n  - id: F1006.002\n    name: 'Account Takeover: Exposed Login Credential'\n    tactic: initial-access\n    source: f3\n  - id: T1110.003\n    name: 'Brute Force: Password Spraying'\n    tactic: initial-access\n    source: attack\n  - id: T1550\n    name: Use Alternate Authentication Material\n    tactic: initial-access\n    source: attack\n  - id: F1004\n    name: Access with Stolen Session Cookie\n    tactic: initial-access\n    source: f3\n---\n\n# Building Identity Federation with SAML Azure AD\n\n## Overview\n\nIdentity federation enables users authenticated by one identity provider to access resources managed by another without maintaining separate credentials. This skill covers establishing SAML 2.0 federation between an organization's on-premises Active Directory (via AD FS or third-party IdP) and Microsoft Entra ID (formerly Azure AD), as well as configuring federated SSO for third-party SaaS applications. Federation eliminates password synchronization concerns and keeps authentication authority on-premises while extending SSO to cloud resources.\n\n\n## When to Use\n\n- When deploying or configuring building identity federation with saml azure ad 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- On-premises Active Directory domain\n- AD FS 2019+ or third-party SAML IdP (Okta, Ping, etc.)\n- Microsoft Entra ID tenant (P1 or P2 license recommended)\n- Azure AD Connect (if using hybrid identity with password hash sync as backup)\n- Public TLS certificate for federation endpoint\n- DNS records for federation service name\n\n## Core Concepts\n\n### Federation Models\n\n| Model | Authentication Authority | Use Case |\n|-------|------------------------|----------|\n| Federated (AD FS) | On-premises AD FS | Regulatory requirement to keep auth on-prem |\n| Managed (PHS) | Azure AD with password hash sync | Simplest cloud auth, AD FS not needed |\n| Managed (PTA) | On-premises via pass-through agent | Cloud auth validated against on-prem AD |\n| Third-Party Federation | External IdP (Okta, Ping) | Multi-IdP environment |\n\n### SAML Federation Architecture\n\n```\nUser → Cloud App (SP)\n   │\n   └── Redirect to Azure AD\n          │\n          ├── Azure AD checks federated domain\n          │\n          └── Redirect to on-premises AD FS\n                 │\n                 ├── AD FS authenticates against Active Directory\n                 │\n                 ├── AD FS issues SAML token\n                 │\n                 └── Token posted back to Azure AD\n                        │\n                        ├── Azure AD validates federation trust\n                        │\n                        ├── Azure AD issues its own token\n                        │\n                        └── User receives access token for cloud app\n```\n\n### Federation Trust Components\n\n| Component | Description |\n|-----------|-------------|\n| Token-Signing Certificate | X.509 certificate used by IdP to sign SAML assertions |\n| Federation Metadata | XML document describing IdP endpoints and capabilities |\n| Relying Party Trust | Configuration in AD FS for each SP (Azure AD) |\n| Claims Rules | Transform AD attributes into SAML claims |\n| Issuer URI | Unique identifier for the IdP (entity ID) |\n\n## Workflow\n\n### Step 1: Prepare AD FS Infrastructure\n\n```powershell\n# Install AD FS role\nInstall-WindowsFeature ADFS-Federation -IncludeManagementTools\n\n# Configure AD FS farm\nInstall-AdfsFarm `\n    -CertificateThumbprint $certThumbprint `\n    -FederationServiceDisplayName \"Corp Federation Service\" `\n    -FederationServiceName \"fs.corp.example.com\" `\n    -ServiceAccountCredential $gmsaCredential\n\n# Verify AD FS is operational\nGet-AdfsProperties | Select-Object HostName, Identifier, FederationPassiveAddress\n```\n\n### Step 2: Configure Azure AD Federated Domain\n\n```powershell\n# Install Microsoft Graph PowerShell module\nInstall-Module Microsoft.Graph -Scope CurrentUser\n\n# Connect to Microsoft Graph\nConnect-MgGraph -Scopes \"Domain.ReadWrite.All\"\n\n# Convert managed domain to federated\n# Using AD FS federation metadata URL\n$domainId = \"corp.example.com\"\n$federationConfig = @{\n    issuerUri = \"http:\u002F\u002Ffs.corp.example.com\u002Fadfs\u002Fservices\u002Ftrust\"\n    metadataExchangeUri = \"https:\u002F\u002Ffs.corp.example.com\u002Fadfs\u002Fservices\u002Ftrust\u002Fmex\"\n    passiveSignInUri = \"https:\u002F\u002Ffs.corp.example.com\u002Fadfs\u002Fls\u002F\"\n    signOutUri = \"https:\u002F\u002Ffs.corp.example.com\u002Fadfs\u002Fls\u002F?wa=wsignout1.0\"\n    signingCertificate = $base64Cert\n    preferredAuthenticationProtocol = \"saml\"\n}\n\n# Apply federation settings to domain\nNew-MgDomainFederationConfiguration -DomainId $domainId -BodyParameter $federationConfig\n```\n\n### Step 3: Configure AD FS Claims Rules\n\n```powershell\n# Add Relying Party Trust for Azure AD\nAdd-AdfsRelyingPartyTrust `\n    -Name \"Microsoft Office 365 Identity Platform\" `\n    -MetadataUrl \"https:\u002F\u002Fnexus.microsoftonline-p.com\u002Ffederationmetadata\u002F2007-06\u002Ffederationmetadata.xml\"\n\n# Configure claim rules\n$rules = @\"\n@RuleTemplate = \"LdapClaims\"\n@RuleName = \"Extract AD Attributes\"\nc:[Type == \"http:\u002F\u002Fschemas.microsoft.com\u002Fws\u002F2008\u002F06\u002Fidentity\u002Fclaims\u002Fwindowsaccountname\",\n   Issuer == \"AD AUTHORITY\"]\n=> issue(store = \"Active Directory\",\n   types = (\"http:\u002F\u002Fschemas.xmlsoap.org\u002Fclaims\u002FUPN\",\n            \"http:\u002F\u002Fschemas.xmlsoap.org\u002Fws\u002F2005\u002F05\u002Fidentity\u002Fclaims\u002Femailaddress\",\n            \"http:\u002F\u002Fschemas.xmlsoap.org\u002Fws\u002F2005\u002F05\u002Fidentity\u002Fclaims\u002Fgivenname\",\n            \"http:\u002F\u002Fschemas.xmlsoap.org\u002Fws\u002F2005\u002F05\u002Fidentity\u002Fclaims\u002Fsurname\"),\n   query = \";userPrincipalName,mail,givenName,sn;{0}\",\n   param = c.Value);\n\n@RuleTemplate = \"PassThroughClaims\"\n@RuleName = \"Pass Through UPN as NameID\"\nc:[Type == \"http:\u002F\u002Fschemas.xmlsoap.org\u002Fclaims\u002FUPN\"]\n=> issue(Type = \"http:\u002F\u002Fschemas.xmlsoap.org\u002Fws\u002F2005\u002F05\u002Fidentity\u002Fclaims\u002Fnameidentifier\",\n   Issuer = c.Issuer, OriginalIssuer = c.OriginalIssuer,\n   Value = c.Value,\n   ValueType = c.ValueType,\n   Properties[\"http:\u002F\u002Fschemas.xmlsoap.org\u002Fws\u002F2005\u002F05\u002Fidentity\u002Fclaimproperties\u002Fformat\"]\n       = \"urn:oasis:names:tc:SAML:2.0:nameid-format:persistent\");\n\"@\n\nSet-AdfsRelyingPartyTrust `\n    -TargetName \"Microsoft Office 365 Identity Platform\" `\n    -IssuanceTransformRules $rules\n```\n\n### Step 4: Configure Third-Party SaaS Federation\n\nFor each SaaS application that supports SAML SSO via Azure AD:\n\n1. Navigate to Microsoft Entra Admin Center > Enterprise Applications\n2. Add the application from the gallery (or create custom SAML)\n3. Configure Single Sign-On > SAML:\n   - Identifier (Entity ID): Application's entity ID\n   - Reply URL (ACS): Application's assertion consumer service URL\n   - Sign-on URL: Application's login URL\n4. Map user attributes\u002Fclaims:\n   - NameID: user.userprincipalname (email format)\n   - Additional claims as required by the application\n5. Download the Federation Metadata XML or certificate\n6. Configure the SaaS app with Azure AD's federation details\n\n### Step 5: Certificate Lifecycle Management\n\nAD FS token-signing certificates expire and must be renewed:\n\n```powershell\n# Check current certificate expiration\nGet-AdfsCertificate -CertificateType Token-Signing | Select-Object Thumbprint, NotAfter\n\n# AD FS supports auto-rollover (enabled by default)\nGet-AdfsProperties | Select-Object AutoCertificateRollover\n\n# If manual rotation is needed:\n# 1. Add new certificate as secondary\nSet-AdfsCertificate -CertificateType Token-Signing -Thumbprint $newThumbprint -IsPrimary $false\n# 2. Update Azure AD with new certificate\n# 3. Promote to primary\nSet-AdfsCertificate -CertificateType Token-Signing -Thumbprint $newThumbprint -IsPrimary $true\n# 4. Remove old certificate\nRemove-AdfsCertificate -CertificateType Token-Signing -Thumbprint $oldThumbprint\n```\n\n## Validation Checklist\n\n- [ ] AD FS farm operational with valid TLS and token-signing certificates\n- [ ] Azure AD domain configured as federated with correct metadata\n- [ ] Claims rules properly transform AD attributes to SAML assertions\n- [ ] Test user can authenticate through federation flow end-to-end\n- [ ] MFA enforced at AD FS or Azure AD conditional access level\n- [ ] Certificate auto-rollover enabled or manual rotation scheduled\n- [ ] Federation metadata endpoint publicly accessible\n- [ ] Smart lockout configured to prevent brute force\n- [ ] Extranet lockout policies configured on AD FS\n- [ ] Monitoring configured for AD FS health and certificate expiry\n- [ ] Disaster recovery: managed authentication fallback documented\n\n## References\n\n- [Microsoft Entra Federation Documentation](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fidentity\u002Fhybrid\u002Fconnect\u002Fwhatis-fed)\n- [AD FS Design Guide](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fwindows-server\u002Fidentity\u002Fad-fs\u002Fdesign\u002Fad-fs-design-guide)\n- [Configure AD FS for Azure AD Federation](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fidentity\u002Fhybrid\u002Fconnect\u002Fhow-to-connect-fed-management)\n- [SAML 2.0 Authentication - OASIS](https:\u002F\u002Fdocs.oasis-open.org\u002Fsecurity\u002Fsaml\u002Fv2.0\u002F)\n","# Building Identity Federation with SAML Azure AD\n\n## Overview\n\nIdentity federation enables users authenticated by one identity provider to access resources managed by another without maintaining separate credentials. This skill covers establishing SAML 2.0 federation between an organization's on-premises Active Directory (via AD FS or third-party IdP) and Microsoft Entra ID (formerly Azure AD), as well as configuring federated SSO for third-party SaaS applications. Federation eliminates password synchronization concerns and keeps authentication authority on-premises while extending SSO to cloud resources.\n\n\n## When to Use\n\n- When deploying or configuring building identity federation with saml azure ad 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- On-premises Active Directory domain\n- AD FS 2019+ or third-party SAML IdP (Okta, Ping, etc.)\n- Microsoft Entra ID tenant (P1 or P2 license recommended)\n- Azure AD Connect (if using hybrid identity with password hash sync as backup)\n- Public TLS certificate for federation endpoint\n- DNS records for federation service name\n\n## Core Concepts\n\n### Federation Models\n\n| Model | Authentication Authority | Use Case |\n|-------|------------------------|----------|\n| Federated (AD FS) | On-premises AD FS | Regulatory requirement to keep auth on-prem |\n| Managed (PHS) | Azure AD with password hash sync | Simplest cloud auth, AD FS not needed |\n| Managed (PTA) | On-premises via pass-through agent | Cloud auth validated against on-prem AD |\n| Third-Party Federation | External IdP (Okta, Ping) | Multi-IdP environment |\n\n### SAML Federation Architecture\n\n```\nUser → Cloud App (SP)\n   │\n   └── Redirect to Azure AD\n          │\n          ├── Azure AD checks federated domain\n          │\n          └── Redirect to on-premises AD FS\n                 │\n                 ├── AD FS authenticates against Active Directory\n                 │\n                 ├── AD FS issues SAML token\n                 │\n                 └── Token posted back to Azure AD\n                        │\n                        ├── Azure AD validates federation trust\n                        │\n                        ├── Azure AD issues its own token\n                        │\n                        └── User receives access token for cloud app\n```\n\n### Federation Trust Components\n\n| Component | Description |\n|-----------|-------------|\n| Token-Signing Certificate | X.509 certificate used by IdP to sign SAML assertions |\n| Federation Metadata | XML document describing IdP endpoints and capabilities |\n| Relying Party Trust | Configuration in AD FS for each SP (Azure AD) |\n| Claims Rules | Transform AD attributes into SAML claims |\n| Issuer URI | Unique identifier for the IdP (entity ID) |\n\n## Workflow\n\n### Step 1: Prepare AD FS Infrastructure\n\n```powershell\n# Install AD FS role\nInstall-WindowsFeature ADFS-Federation -IncludeManagementTools\n\n# Configure AD FS farm\nInstall-AdfsFarm `\n    -CertificateThumbprint $certThumbprint `\n    -FederationServiceDisplayName \"Corp Federation Service\" `\n    -FederationServiceName \"fs.corp.example.com\" `\n    -ServiceAccountCredential $gmsaCredential\n\n# Verify AD FS is operational\nGet-AdfsProperties | Select-Object HostName, Identifier, FederationPassiveAddress\n```\n\n### Step 2: Configure Azure AD Federated Domain\n\n```powershell\n# Install Microsoft Graph PowerShell module\nInstall-Module Microsoft.Graph -Scope CurrentUser\n\n# Connect to Microsoft Graph\nConnect-MgGraph -Scopes \"Domain.ReadWrite.All\"\n\n# Convert managed domain to federated\n# Using AD FS federation metadata URL\n$domainId = \"corp.example.com\"\n$federationConfig = @{\n    issuerUri = \"http:\u002F\u002Ffs.corp.example.com\u002Fadfs\u002Fservices\u002Ftrust\"\n    metadataExchangeUri = \"https:\u002F\u002Ffs.corp.example.com\u002Fadfs\u002Fservices\u002Ftrust\u002Fmex\"\n    passiveSignInUri = \"https:\u002F\u002Ffs.corp.example.com\u002Fadfs\u002Fls\u002F\"\n    signOutUri = \"https:\u002F\u002Ffs.corp.example.com\u002Fadfs\u002Fls\u002F?wa=wsignout1.0\"\n    signingCertificate = $base64Cert\n    preferredAuthenticationProtocol = \"saml\"\n}\n\n# Apply federation settings to domain\nNew-MgDomainFederationConfiguration -DomainId $domainId -BodyParameter $federationConfig\n```\n\n### Step 3: Configure AD FS Claims Rules\n\n```powershell\n# Add Relying Party Trust for Azure AD\nAdd-AdfsRelyingPartyTrust `\n    -Name \"Microsoft Office 365 Identity Platform\" `\n    -MetadataUrl \"https:\u002F\u002Fnexus.microsoftonline-p.com\u002Ffederationmetadata\u002F2007-06\u002Ffederationmetadata.xml\"\n\n# Configure claim rules\n$rules = @\"\n@RuleTemplate = \"LdapClaims\"\n@RuleName = \"Extract AD Attributes\"\nc:[Type == \"http:\u002F\u002Fschemas.microsoft.com\u002Fws\u002F2008\u002F06\u002Fidentity\u002Fclaims\u002Fwindowsaccountname\",\n   Issuer == \"AD AUTHORITY\"]\n=> issue(store = \"Active Directory\",\n   types = (\"http:\u002F\u002Fschemas.xmlsoap.org\u002Fclaims\u002FUPN\",\n            \"http:\u002F\u002Fschemas.xmlsoap.org\u002Fws\u002F2005\u002F05\u002Fidentity\u002Fclaims\u002Femailaddress\",\n            \"http:\u002F\u002Fschemas.xmlsoap.org\u002Fws\u002F2005\u002F05\u002Fidentity\u002Fclaims\u002Fgivenname\",\n            \"http:\u002F\u002Fschemas.xmlsoap.org\u002Fws\u002F2005\u002F05\u002Fidentity\u002Fclaims\u002Fsurname\"),\n   query = \";userPrincipalName,mail,givenName,sn;{0}\",\n   param = c.Value);\n\n@RuleTemplate = \"PassThroughClaims\"\n@RuleName = \"Pass Through UPN as NameID\"\nc:[Type == \"http:\u002F\u002Fschemas.xmlsoap.org\u002Fclaims\u002FUPN\"]\n=> issue(Type = \"http:\u002F\u002Fschemas.xmlsoap.org\u002Fws\u002F2005\u002F05\u002Fidentity\u002Fclaims\u002Fnameidentifier\",\n   Issuer = c.Issuer, OriginalIssuer = c.OriginalIssuer,\n   Value = c.Value,\n   ValueType = c.ValueType,\n   Properties[\"http:\u002F\u002Fschemas.xmlsoap.org\u002Fws\u002F2005\u002F05\u002Fidentity\u002Fclaimproperties\u002Fformat\"]\n       = \"urn:oasis:names:tc:SAML:2.0:nameid-format:persistent\");\n\"@\n\nSet-AdfsRelyingPartyTrust `\n    -TargetName \"Microsoft Office 365 Identity Platform\" `\n    -IssuanceTransformRules $rules\n```\n\n### Step 4: Configure Third-Party SaaS Federation\n\nFor each SaaS application that supports SAML SSO via Azure AD:\n\n1. Navigate to Microsoft Entra Admin Center > Enterprise Applications\n2. Add the application from the gallery (or create custom SAML)\n3. Configure Single Sign-On > SAML:\n   - Identifier (Entity ID): Application's entity ID\n   - Reply URL (ACS): Application's assertion consumer service URL\n   - Sign-on URL: Application's login URL\n4. Map user attributes\u002Fclaims:\n   - NameID: user.userprincipalname (email format)\n   - Additional claims as required by the application\n5. Download the Federation Metadata XML or certificate\n6. Configure the SaaS app with Azure AD's federation details\n\n### Step 5: Certificate Lifecycle Management\n\nAD FS token-signing certificates expire and must be renewed:\n\n```powershell\n# Check current certificate expiration\nGet-AdfsCertificate -CertificateType Token-Signing | Select-Object Thumbprint, NotAfter\n\n# AD FS supports auto-rollover (enabled by default)\nGet-AdfsProperties | Select-Object AutoCertificateRollover\n\n# If manual rotation is needed:\n# 1. Add new certificate as secondary\nSet-AdfsCertificate -CertificateType Token-Signing -Thumbprint $newThumbprint -IsPrimary $false\n# 2. Update Azure AD with new certificate\n# 3. Promote to primary\nSet-AdfsCertificate -CertificateType Token-Signing -Thumbprint $newThumbprint -IsPrimary $true\n# 4. Remove old certificate\nRemove-AdfsCertificate -CertificateType Token-Signing -Thumbprint $oldThumbprint\n```\n\n## Validation Checklist\n\n- [ ] AD FS farm operational with valid TLS and token-signing certificates\n- [ ] Azure AD domain configured as federated with correct metadata\n- [ ] Claims rules properly transform AD attributes to SAML assertions\n- [ ] Test user can authenticate through federation flow end-to-end\n- [ ] MFA enforced at AD FS or Azure AD conditional access level\n- [ ] Certificate auto-rollover enabled or manual rotation scheduled\n- [ ] Federation metadata endpoint publicly accessible\n- [ ] Smart lockout configured to prevent brute force\n- [ ] Extranet lockout policies configured on AD FS\n- [ ] Monitoring configured for AD FS health and certificate expiry\n- [ ] Disaster recovery: managed authentication fallback documented\n\n## References\n\n- [Microsoft Entra Federation Documentation](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fidentity\u002Fhybrid\u002Fconnect\u002Fwhatis-fed)\n- [AD FS Design Guide](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fwindows-server\u002Fidentity\u002Fad-fs\u002Fdesign\u002Fad-fs-design-guide)\n- [Configure AD FS for Azure AD Federation](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fentra\u002Fidentity\u002Fhybrid\u002Fconnect\u002Fhow-to-connect-fed-management)\n- [SAML 2.0 Authentication - OASIS](https:\u002F\u002Fdocs.oasis-open.org\u002Fsecurity\u002Fsaml\u002Fv2.0\u002F)\n",{"name":5,"tags":24,"author":33,"domain":34,"license":15,"version":35,"mitre_f3":36,"nist_csf":59,"subdomain":64,"description":7,"mitre_attack":65},[25,26,27,28,29,30,31,32],"saml","azure-ad","entra-id","federation","identity","sso","adfs","hybrid-identity","mahipal","cybersecurity","1.0",{"tactics":37,"version":40,"techniques":41},[38,39],"initial-access","positioning","1.1",[42,46,49,53,56],{"id":43,"name":44,"source":45,"tactic":38},"F1006","Account Takeover","f3",{"id":47,"name":48,"source":45,"tactic":38},"F1006.002","Account Takeover: Exposed Login Credential",{"id":50,"name":51,"source":52,"tactic":38},"T1110.003","Brute Force: Password Spraying","attack",{"id":54,"name":55,"source":52,"tactic":38},"T1550","Use Alternate Authentication Material",{"id":57,"name":58,"source":45,"tactic":38},"F1004","Access with Stolen Session Cookie",[60,61,62,63],"PR.AA-01","PR.AA-02","PR.AA-05","PR.AA-06","identity-access-management",[66,67,68,69,50],"T1606.002","T1556.007","T1484.002","T1078.004","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","03-逆向工程\u002Fbuilding-identity-federation-with-saml-azure-ad",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":79,"prompt":89,"zipAvailable":90},[80,83,86],{"tool":81,"command":82},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill building-identity-federation-with-saml-azure-ad",{"tool":84,"command":85},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill building-identity-federation-with-saml-azure-ad",{"tool":87,"command":88},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill building-identity-federation-with-saml-azure-ad","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F03-逆向工程\u002Fbuilding-identity-federation-with-saml-azure-ad\u002FSKILL.md",true,[92,98,102],{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fapi-reference.md","REFERENCE","参考文档",1598,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F03-逆向工程\u002Fbuilding-identity-federation-with-saml-azure-ad\u002Freferences\u002Fapi-reference.md",{"path":99,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fstandards.md",1761,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F03-逆向工程\u002Fbuilding-identity-federation-with-saml-azure-ad\u002Freferences\u002Fstandards.md",{"path":103,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fworkflows.md",4439,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F03-逆向工程\u002Fbuilding-identity-federation-with-saml-azure-ad\u002Freferences\u002Fworkflows.md",[107,116,121,128,135,142],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":111,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":115},"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":117,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":111,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":115},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":111,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":115},"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":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":111,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":115},"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":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":111,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":115},"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":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":111,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":115},"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",[],[]]