feat: add isTokenEndpointIpHeaderTrusted field to Client #775
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.
Changes
This PR adds support for the
is_token_endpoint_ip_header_trustedproperty to theClientclass in the Management API.Classes and methods added:
isTokenEndpointIpHeaderTrustedfield toClientclass with@JsonPropertyannotationgetIsTokenEndpointIpHeaderTrusted()getter method with JavaDocsetIsTokenEndpointIpHeaderTrusted(Boolean)setter method with JavaDocSummary of usage:
This property controls whether the token endpoint trusts IP headers for the application, which is relevant for scenarios where the application operates behind proxies or load balancers.
References
Testing
This change has been tested with comprehensive unit tests covering both serialization and deserialization:
ClientTest.shouldSerialize()to verify the field serializes correctly to JSONClientTest.shouldDeserialize()to verify the field deserializes correctly from JSON./gradlew test --tests ClientTestTest coverage includes:
truetrue@JsonPropertymapping to snake_case API field nameChecklist