Skip to content

feat: add optional accountId support to CP4D authenticator - #371

Open
jacek-midura wants to merge 1 commit into
IBM:mainfrom
jacek-midura:add-account-id
Open

jacek-midura wants to merge 1 commit into
IBM:mainfrom
jacek-midura:add-account-id

Conversation

@jacek-midura

@jacek-midura jacek-midura commented Sep 24, 2026 •

Copy link
Copy Markdown
Member

issue: https://github.ibm.com/arf/planning-sdk-squad/issues/4470

Add an optional accountId field to both CloudPakForDataAuthenticator and Cp4dTokenManager. When provided, the value is included as account_id in the POST /v1/authorize request body.

When reading from external configuration (env vars / credentials file), the property CP4D_ACCOUNT_ID is camelCased to cp4dAccountId by readExternalSources and remapped to accountId before constructing the authenticator.

Checklist
  • npm test passes (tip: npm run lint-fix can correct most style issues)
  • tests are included
  • documentation is changed or added

Add an optional accountId field to both CloudPakForDataAuthenticator and
Cp4dTokenManager. When provided, the value is included as account_id in
the POST /v1/authorize request body.

When reading from external configuration (env vars / credentials file),
the property CP4D_ACCOUNT_ID is camelCased to cp4dAccountId by
readExternalSources and remapped to accountId before constructing the
authenticator.

Signed-off-by: Jacek Midura <jacek.midura@pl.ibm.com>
@CLAassistant

CLAassistant commented Sep 24, 2026 •

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

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.

2 participants