Skip to content

chore: redirect to core lib for runtime actions #171

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

Merged
moritzraho merged 2 commits into from
Feb 13, 2026
Merged

chore: redirect to core lib for runtime actions #171

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f49fc77
chore: redirect to core lib for runtime actions
moritzraho Jan 19, 2026
f0e828d
more details
moritzraho Jan 19, 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
5 changes: 2 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,10 +92,9 @@ const token = await getToken('my-config')

## Running in an Adobe I/O Runtime action

**Note that Adobe Developer App Builder applications should not own the responsibility to generate their own IMS access tokens.
We strongly discourage this approach in favor of more secure implementation patterns that are documented in our [App Builder Security Guide](https://developer.adobe.com/app-builder/docs/guides/security/#runtime-specific-guidelines).**
**Note: Please prefer the more lightweight [@adobe/aio-lib-core-auth](https://github.com/adobe-developer-platform/app-builder-aio-lib-core-auth) library to generate OAuth tokens from an Adobe I/O Runtime action. The core library focuses on generating OAuth tokens efficiently and doesn't rely on the complex context/plugin logic needed in the CLI. It also uses in-memory caching instead of App Builder State storage, which may run into usage limitations**

The AIO IMS Library can also be used in an Adobe I/O Runtime action. In this case the IMS configuration must be set beforehand. The library is relying on the [Adobe I/O Cloud State Library](https://github.com/adobe/aio-lib-state) to persist the access tokens across action invocations and reduce the number of requests to IMS.
The AIO IMS Library can also be used in an Adobe I/O Runtime action. In this case the IMS configuration must be set beforehand. The library is relying on the [Adobe App Builder State Library](https://github.com/adobe/aio-lib-state) to persist the access tokens across action invocations and reduce the number of requests to IMS.

Here is an Adobe I/O Runtime action example that leverages the AIO IMS:

Expand Down