Skip to content

Conversation

@mpern
Copy link
Contributor

@mpern mpern commented Oct 24, 2025

Context

SAP/cloud-sdk-java-backlog#ISSUENUMBER.

Add support for the resource=urn:sap:identity:application:provider:clientid: resource definition for app2app token requests to reduce the number of required tokens from one per app2app "Dependency Name" to one per provider application

Feature scope:

  • Add support for resource=urn:sap:identity:application:provider:clientid:<client-id-provider>:apptid:<tenant-id-provider> for app2app token reuests - ref Exposing APIs (SAP-internal)

Definition of Done

  • Functionality scope stated & covered
  • Tests cover the scope above
  • Error handling created / updated & covered by the tests above
  • Documentation updated
  • Release notes updated

Comment on lines +647 to +649
"urn:sap:identity:application:provider:clientid:provider-client-id:apptid:provider-tenant-id",
"app_tid",
PROVIDER_TENANT_ID));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately, the term provider is ambiguous in this context, and it becomes pretty apparent here 😅

  • In the context of Cloud SDK, provider typically means the BTP subaccount in which this currently running Java application is hosted, i.e. the provider tenant
  • In the context of IAS App2App, provider refers to the target system that is providing the API, and the currently running Java application acts as the consumer

I don't see an easy way to resolve this confusion, other than adding an explicit comment here that the difference apptid:provider-tenant-id vs. app_tid=PROVIDER_TENANT_ID is expected and intended.

Copy link
Member

@MatKuhr MatKuhr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, ty for contributing 🥳

Adding a small release note would be good, but we can also do that in a separate PR to accelerate merging this. @newtork would leave that up to you depending on when we want to press the release button 😉

@CharlesDuboisSAP CharlesDuboisSAP merged commit e2643f5 into SAP:main Oct 30, 2025
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants