/sap-btp-cloud-identity-services
SAP Cloud Identity Services for BTP applications: Identity Authentication (IAS), Identity Provisioning (IPS), and Authorization Management (AMS). Use when configuring authentication for BTP apps, setting up OIDC or SAML app registrations, federating corporate identity providers,
$ npx -y skills add secondsky/sap-skills --skill sap-btp-cloud-identity-services --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/sap-btp-cloud-identity-services
Context preview
The summary Claude sees to decide when to auto-load this skill.
SAP Cloud Identity Services for BTP applications: Identity Authentication (IAS), Identity Provisioning (IPS), and Authorization Management (AMS). Use when configuring authentication for BTP apps, setting up OIDC or SAML app registrations, federating corporate identity providers,
SKILL.md
sap-btp-cloud-identity-services.SKILL.mdname: sap-btp-cloud-identity-services
description: |
SAP Cloud Identity Services for BTP applications: Identity Authentication (IAS), Identity Provisioning (IPS), and Authorization Management (AMS). Use when configuring authentication for BTP apps, setting up OIDC or SAML app registrations, federating corporate identity providers, establishing subaccount trust, provisioning users, writing AMS authorization policies, migrating from XSUAA to IAS-based authentication, or troubleshooting token and trust errors.
license: GPL-3.0
metadata:
maintainer: "Eduard Jiglau"
maintainer_email: "hello@sap-ai-skills.com"
website: "https://sap-ai-skills.com"
version: "2.4.1"
last_verified: "2026-06-12"
documentation_source: https://help.sap.com/docs/cloud-identity-services
ias_docs: https://github.com/SAP-docs/btp-cloud-identity-services
integration_guide: https://help.sap.com/viewer/b95c3d5bab324a3a8409eee5267a5b75/Cloud/en-US/27947dfb325047018603446439050a6b.html
cap_ias_guide: https://cap.cloud.sap/docs/guides/integration/platform/ias-xsuaa
SAP Cloud Identity Services
SAP Cloud Identity Services are a group of services on SAP BTP that manage identity and access across cloud and on-premise systems. They provide single sign-on, user provisioning, and policy-based authorization.
The services comprise:
- **Identity Authentication (IAS)** — cloud-based authentication, SSO (OIDC/SAML 2.0), corporate IdP federation, conditional authentication, and user store management. Acts as the identity provider for SAP BTP applications.
- **Identity Provisioning (IPS)** — identity lifecycle management as a service. Synchronizes users and groups between source and target systems (SAP and non-SAP) with full and delta read modes, real-time provisioning, and transformation support.
- **Identity Directory** — the central user store. Provides SCIM 2.0 REST API, custom schemas, and generates the Global User ID distributed by IPS to SAP cloud applications.
- **Authorization Management (AMS)** — policy-based authorization for BTP applications. Developers define policies in Data Control Language (DCL); administrators refine and assign them via the administration console.
Related Skills
- **sap-btp-connectivity** — destination service and connection authentication mechanics (OAuth client credentials, principal propagation through Cloud Connector)
- **sap-cap-capire** — CAP application-level auth usage (role templates, @requires annotations, cds deploy with xs-security.json)
- **sap-btp-best-practices** — high-level security governance and production deployment patterns
- **sap-btp-cloud-platform** — BTP account setup, subaccount configuration, service instance creation
When to Use This Skill
- Registering an OIDC or SAML 2.0 application in IAS
- Configuring corporate identity provider federation (IdP proxy)
- Establishing trust between a BTP subaccount and an IAS tenant
- Setting up Identity Provisioning source/target systems and jobs
- Writing or refining AMS authorization policies (DCL)
- Migrating from XSUAA to IAS-based authentication
- Troubleshooting token validation, audience, or issuer mismatch errors
- Configuring conditional authentication (risk-based, MFA)
- Integrating IAS with the SAP BTP Identity service (automatic OIDC app creation)
Quick Reference
| Service | Purpose | Key Objects | |---------|---------|-------------| | IAS | Authentication & SSO | Applications (OIDC/SAML), IdPs, conditional auth, user store | | IPS | User/group provisioning | Source systems, target systems, proxy systems, transformations, jobs | | Identity Directory | User persistence | Users, groups, custom schemas, Global User ID | | AMS | Policy-based authorization | Authorization policies, DCL rules, policy templates, restrictions |
Identity Authentication (IAS)
IAS is the entry point for authentication in SAP BTP applications. It supports OIDC and SAML 2.0 protocols, acts as an identity provider or a proxy to corporate IdPs, and provides conditional authentication based on user attributes, email domain, user group, or IP range.
Application Registration
Register applications in the IAS admin console under **Applications and Resources** > **Applications**. Each application defines:
- **Application Type** — OIDC or SAML 2.0
- **Trust Configuration** — SP metadata upload (SAML) or redirect URIs (OIDC)
- **Authentication** — method, conditional rules, IdP selection
- **User Attributes** — which attributes are sent in tokens/assertions
When using the **SAP BTP Identity service** (`xsuaa` replacement), the service instance automatically creates an OIDC application in IAS. No manual registration is needed.
Corporate IdP Federation
IAS can act as a proxy: end users authenticate at a corporate IdP (Azure AD, Okta, etc.), and IAS bridges the token for SAP applications. Configure under **Applications and Resources** > **Corporate Identity Providers**.
For details, see `references/identity-authentication.md`.
Identity Provisioning (IPS)
IPS synchronizes users and groups between systems. It supports source, target, and proxy system types with configurable transformations and scheduling.
Key Concepts
- **Source systems** — read users/groups from (e.g., SAP SuccessFactors, Azure AD, SAP S/4HANA Cloud)
- **Target systems** — write users/groups to (e.g., IAS tenant, SAP BTP XSUAA, SAP Analytics Cloud)
- **Proxy systems** — hybrid scenarios where IPS reads from one system and writes through another
- **Transformations** — JSON-based attribute mappings between source and target schemas
- **Jobs** — scheduled or on-demand provisioning runs (full or delta read)
- **Real-time provisioning** — immediate entity propagation from source to target
For details, see `references/identity-provisioning.md`.
Authorization Management (AMS)
AMS enables policy-based, instance-level authorization for BTP applications. Developers define authorization policies in **Data Control Language (DCL)** — an
Read more
name: sap-btp-cloud-identity-services description: | SAP Cloud Identity Services for BTP applications: Identity Authentication (IAS), Identity Provisioning (IPS), and Authorization Management (AMS). Use when configuring authentication for BTP apps, setting up OIDC or SAML app registrations, federating corporate identity providers, establishing subaccount trust, provisioning users, writing AMS authorization policies, migrating from XSUAA to IAS-based authentication, or troubleshooting token and trust errors. license: GPL-3.0 metadata: maintainer: "Eduard Jiglau" maintainer_email: "hello@sap-ai-skills.com" website: "https://sap-ai-skills.com" version: "2.4.1" last_verified: "2026-06-12" documentation_source: https://help.sap.com/docs/cloud-identity-services ias_docs: https://github.com/SAP-docs/btp-cloud-identity-services integration_guide: https://help.sap.com/viewer/b95c3d5bab324a3a8409eee5267a5b75/Cloud/en-US/27947dfb325047018603446439050a6b.html cap_ias_guide: https://cap.cloud.sap/docs/guides/integration/platform/ias-xsuaa
SAP Cloud Identity Services
SAP Cloud Identity Services are a group of services on SAP BTP that manage identity and access across cloud and on-premise systems. They provide single sign-on, user provisioning, and policy-based authorization.
The services comprise:
- **Identity Authentication (IAS)** — cloud-based authentication, SSO (OIDC/SAML 2.0), corporate IdP federation, conditional authentication, and user store management. Acts as the identity provider for SAP BTP applications.
- **Identity Provisioning (IPS)** — identity lifecycle management as a service. Synchronizes users and groups between source and target systems (SAP and non-SAP) with full and delta read modes, real-time provisioning, and transformation support.
- **Identity Directory** — the central user store. Provides SCIM 2.0 REST API, custom schemas, and generates the Global User ID distributed by IPS to SAP cloud applications.
- **Authorization Management (AMS)** — policy-based authorization for BTP applications. Developers define policies in Data Control Language (DCL); administrators refine and assign them via the administration console.
Related Skills
- **sap-btp-connectivity** — destination service and connection authentication mechanics (OAuth client credentials, principal propagation through Cloud Connector)
- **sap-cap-capire** — CAP application-level auth usage (role templates, @requires annotations, cds deploy with xs-security.json)
- **sap-btp-best-practices** — high-level security governance and production deployment patterns
- **sap-btp-cloud-platform** — BTP account setup, subaccount configuration, service instance creation
When to Use This Skill
- Registering an OIDC or SAML 2.0 application in IAS
- Configuring corporate identity provider federation (IdP proxy)
- Establishing trust between a BTP subaccount and an IAS tenant
- Setting up Identity Provisioning source/target systems and jobs
- Writing or refining AMS authorization policies (DCL)
- Migrating from XSUAA to IAS-based authentication
- Troubleshooting token validation, audience, or issuer mismatch errors
- Configuring conditional authentication (risk-based, MFA)
- Integrating IAS with the SAP BTP Identity service (automatic OIDC app creation)
Quick Reference
| Service | Purpose | Key Objects | |---------|---------|-------------| | IAS | Authentication & SSO | Applications (OIDC/SAML), IdPs, conditional auth, user store | | IPS | User/group provisioning | Source systems, target systems, proxy systems, transformations, jobs | | Identity Directory | User persistence | Users, groups, custom schemas, Global User ID | | AMS | Policy-based authorization | Authorization policies, DCL rules, policy templates, restrictions |
Identity Authentication (IAS)
IAS is the entry point for authentication in SAP BTP applications. It supports OIDC and SAML 2.0 protocols, acts as an identity provider or a proxy to corporate IdPs, and provides conditional authentication based on user attributes, email domain, user group, or IP range.
Application Registration
Register applications in the IAS admin console under **Applications and Resources** > **Applications**. Each application defines:
- **Application Type** — OIDC or SAML 2.0
- **Trust Configuration** — SP metadata upload (SAML) or redirect URIs (OIDC)
- **Authentication** — method, conditional rules, IdP selection
- **User Attributes** — which attributes are sent in tokens/assertions
When using the **SAP BTP Identity service** (`xsuaa` replacement), the service instance automatically creates an OIDC application in IAS. No manual registration is needed.
Corporate IdP Federation
IAS can act as a proxy: end users authenticate at a corporate IdP (Azure AD, Okta, etc.), and IAS bridges the token for SAP applications. Configure under **Applications and Resources** > **Corporate Identity Providers**.
For details, see `references/identity-authentication.md`.
Identity Provisioning (IPS)
IPS synchronizes users and groups between systems. It supports source, target, and proxy system types with configurable transformations and scheduling.
Key Concepts
- **Source systems** — read users/groups from (e.g., SAP SuccessFactors, Azure AD, SAP S/4HANA Cloud)
- **Target systems** — write users/groups to (e.g., IAS tenant, SAP BTP XSUAA, SAP Analytics Cloud)
- **Proxy systems** — hybrid scenarios where IPS reads from one system and writes through another
- **Transformations** — JSON-based attribute mappings between source and target schemas
- **Jobs** — scheduled or on-demand provisioning runs (full or delta read)
- **Real-time provisioning** — immediate entity propagation from source to target
For details, see `references/identity-provisioning.md`.
Authorization Management (AMS)
AMS enables policy-based, instance-level authorization for BTP applications. Developers define authorization policies in **Data Control Language (DCL)** — an
40 SAP development plugins with evidence-tracked verification SAP development plugins for AI coding assistants, with public-source or package-registry verification tracked where available.
Repo: secondsky/sap-skills
Other skills on sap-skills.
- /sap-abap-cds
Comprehensive SAP ABAP CDS (Core Data Services) reference for data modeling, view development, and semantic enrichment. Use when creating CDS views or view entities, defining data models with annotations, working with associations and cardinality, implementing input parameters,
Open skill - /sap-abap
Comprehensive ABAP development skill for SAP systems. Use when writing ABAP code, working with internal tables, structures, ABAP SQL, object-oriented programming, RAP (RESTful Application Programming Model), CDS views, EML statements, ABAP Cloud development, string processing,
Open skill - /sap-ai-core
Guides development with SAP AI Core and SAP AI Launchpad for enterprise AI/ML workloads on SAP BTP. Use when: deploying generative AI models, building orchestration workflows with templating/filtering/grounding, implementing RAG with vector databases, managing ML training
Open skill - /sap-api-policy
Evidence-based assessment of whether an SAP API/interface usage scenario aligns with the SAP API Policy (v.4.2026a). Use whenever someone asks whether a way of calling SAP is allowed/compliant — e.g. Published API vs internal/private/"confidential" API status, "Documented Use",
Open skill - /sap-api-style
This skill provides comprehensive guidance for documenting SAP APIs following the SAP API Style Guide standards. It should be used when creating or reviewing API documentation for REST, OData, Java, JavaScript, .NET, or C/C++ APIs. The skill covers naming conventions,
Open skill - /sap-browser-automation
Use when an agent must inspect or operate an authenticated SAP web UI through an in-app Browser, Microsoft Edge CDP, or an existing Playwright client, especially when SAP SSO reuse, isolated Edge profiles, deterministic target selection, screenshots, or browser bootstrap
Open skill

