Repository navigation
Add test coverage for PRIVATE_KEY_JWT sink credential and 422 PRIVATE_KEY_JWT_NOT_CONFIGURED - #143
Merged
jgarciahospital merged 1 commit intoSep 4, 2026
Conversation
…_KEY_JWT_NOT_CONFIGURED
albertoramosmonagas
requested review from
jgarciahospital,
maheshc01 and
sachinvodafone
as code owners
September 3, 2026 08:26
Closed
Contributor
Author
|
Hi @sachinvodafone and @maheshc01, can you approve and merge? |
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
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
This PR adds the missing test coverage for PRIVATE_KEY_JWT sink credentials in the Population Density Data API. It includes:
The scenarios have been adapted to the Population Density Data API operation and response schema.
Which issue(s) this PR fixes:
Fixes camaraproject/PredictiveConnectivityData#75 (same behaviour as Predictive Connectivity Data)
Special notes for reviewers:
Issue #139 does not require additional specification changes, as the jwksUri pre-configuration requirements and PRIVATE_KEY_JWT_NOT_CONFIGURED response are already documented in the API specification. The relevant missing test coverage is addressed by this PR.
A separate inconsistency was identified in the current specification regarding PRIVATE_KEY_JWT_NOT_CONFIGURED being associated with the 400 response instead of the 422 response. This is intentionally left out of scope and should be handled separately.
Changelog input