DSD-10748: fix internal OTP partner identity after service merge - #1786
nagendra0721 wants to merge 1 commit into
Conversation
Signed-off-by: nagendra0721 <nagendra0718@gmail.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Team Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. Walkthrough
ChangesOTP security selection
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to Internal OTP transaction creation now records identity through the internal security manager, while external OTP behavior remains unchanged. The supplied build and regression results show no current merge-blocking risk. Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Internal OTP requests can fail with
IDA-OTA-011after the service merge: OTP transaction creation uses the primary security manager and stores the configured IDA client ID, while internal authentication validates against the authenticated caller identity. This blocks Resident VID creation and auth lock/unlock requests.Inject
internalAuthSecurityManagerseparately and use it only when building internal OTP transactions. External OTP transactions retain their existing security manager, and partner-ID validation is unchanged.Validation:
IDA-OTA-011before the fix and passed unchanged after it. Additional temporary tests covered a different caller being rejected, usernames without the service-account prefix, and external OTP partner identity; these tests were removed after verification.Summary by CodeRabbit