Skip to content

Document tenant-specific IAS host injection in RequestContext #2474

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
StefanHenke wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Document tenant-specific IAS host injection in RequestContext #2474

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ea82a67
Document tenant-specific IAS host injection in RequestContext
StefanHenke Mar 30, 2026
a4c2585
Update cap-users.md
StefanHenke Apr 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions guides/security/cap-users.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1529,6 +1529,16 @@ Avoid iterating through all subscriber tenants to perform tenant-specific tasks.
Instead, prefer a task-based approach which processes specific subscriber tenants selectively.
:::

To use IAS-based Remote Services in background executions, you must in addition manually inject the tenant-specific IAS host into the created Request Context. Unlike inherited request contexts that automatically carry authentication details, a fresh Request Context lacks the IAS host information required for remote service calls. The host can be retrieved from a `TenantInfo` object provided for example by the `TenantProviderService`.
Copy link
Copy Markdown
Contributor

@renejeglinsky renejeglinsky Apr 2, 2026

Choose a reason for hiding this comment

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

I feel that this would be clearer (as long as it's correct).

Suggested change
To use IAS-based Remote Services in background executions, you must in addition manually inject the tenant-specific IAS host into the created Request Context. Unlike inherited request contexts that automatically carry authentication details, a fresh Request Context lacks the IAS host information required for remote service calls. The host can be retrieved from a `TenantInfo` object provided for example by the `TenantProviderService`.
To use IAS-based Remote Services in background executions, you must in addition manually inject the tenant-specific IAS host into the created Request Context. As background executions need a fresh Request Context, they cannot inherit request contexts that automatically carry authentication details and thereby lack the IAS host information required for remote service calls. The host can be retrieved from a `TenantInfo` object provided for example by the `TenantProviderService`.


```java
TenantInto tenantInfo = ...;
String tenantHost = tenantInfo.get("subscriber").get("tenantHost");
runtime.requestContext().systemUser(tenantId).modifyUser(user->user.setAdditionalAttribute("iss", tenantHost)).run((reqContext) -> {
… //call remote service
});
```

</div>

<div class="impl node">
Expand Down
Loading