Fix HttpSender validation errors that clientId is not set, when clientAlias is used instead by tnleeuw · Pull Request #9882 · frankframework/frankframework
Navigation Menu
{{ message }}
frankframework / frankframework Public
- Notifications You must be signed in to change notification settings
- Fork 81
Merged
nielsm5 merged 1 commit intorelease/9.0from
Nov 13, 2025Merged
Conversation
Copy link Copy Markdown
Contributor
tnleeuw
commented
Nov 12, 2025
tnleeuw
commented
Changes
Fix HttpSender validation errors that clientId is not set, when clientAlias is used instead and the client_id and client_secret can be looked up via the Credential Provider.
Pull Request Checklist
Issues
- This is a 9.0 specific fix for issue HttpSender throwing 'Missing required fields: ClientId, clientSecret' error while valid 'clientAlias' is provided #9503 which blocks NN from upgrading to 9.0
Backports
- Backport PRs N/A
Documentation
- FF! Doc updated (N/A)
- FF! Manual updated (N/A)
- Javadoc updated/generated (N/A)
Tests
- Unit tests added/updated
- E2E/Integration tests added/updated (N/A)
…e Credential Provider
tnleeuw
requested review from
evandongen,
nielsm5 and
philipsens
tnleeuw
self-assigned this
Copy link Copy Markdown
sonarqubecloud
bot
commented
Nov 12, 2025
sonarqubecloud bot commented
Nov 12, 2025
Quality Gate passed
Issues
Measures
evandongen approved these changes Nov 12, 2025
nielsm5 approved these changes Nov 13, 2025
nielsm5
deleted the
issue/ClientAliasAndClientIdValidation
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment