feat(dpav3311) iam keycloak client

[AdamBartosikInfo]

Sensitive Credential Checks

• As the author of these changes, I have checked for any sensitive credentials prior to this review being requested.
• As a reviewer of these changes, I have checked for any sensitive credentials prior to approving this merge.

Motivation and Context

Description

• Describe your changes in detail

How Has This Been Tested?

Screenshots (if appropriate):

Checklist:

• It contains only changes required by issue (does not contain other PR)
• Includes link to an issue (if apply)
• I have added tests to cover my changes.

[github-actions]

OSS Checks Passed

All tracked OSS checks passed in this run.

Total Files	Passed	Failed	Score
13	13	0	100%

Results from commit 65fff65, view the full job summary for detailed results.

♻️ This comment has been updated with latest results.

[nikan-negaresh-informed]

just one point ,

can we confirm that this IAM_INTEGRATION_SERVICE should not require existing Federator_CONSUMER and Federator Producer roles?

what you are building is not a federator so it should inherit those.

If you confirm that, we should be able to approve this

[AdamBartosikInfo]

@nikan-negaresh-informed Confirmed, IAM_INTEGRATION_SERVICE is not a federator and does not need the federator scopes. I removed them: it now gets only the roles scope (it only calls the Keycloak admin API, which reads realm-management from the token). Other clients are unchanged.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud