Add IAM service HTTP client and OAuth consent flow services
What does this MR do and why?
Extract shared HTTP infrastructure for IAM service integrations and introduce the service layer for the OAuth consent flow.
- Introduce
HttpClientto encapsulate URL construction, IAM auth headers, timeout, and transport error handling - Introduce
RedirectUrlValidatorto validate IAM redirect URLs - Refactor
AcceptLoginChallengeServiceto useHttpClient - Add
GetConsentChallengeService,AcceptConsentChallengeService, andRejectConsentChallengeServicefor the consent flow - Log HTTP status codes only on failure; response body logging removed in favour of a more structured error.
The controller wiring these services into the consent flow will be introduced in a follow-up MR.
References
- Main issue: #589572
- AcceptLoginChallengeService was introduced by: !225853 (merged)
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Edited by Daniele Bracciani