fix(api): use correct schema in POST /admin/auth-provider/test (GRO-454) #224
Reference in New Issue
Block a user
Delete Branch "fix/gro-454-test-schema"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
/api/admin/auth-provider/testwas usingputAuthProviderSchema.omit({ clientSecret })which requiresproviderId,displayName,clientId,scopes— but the Settings.tsx frontend only sends{ issuerUrl, internalBaseUrl? }authProviderTestSchema(issuerUrl + internalBaseUrl) which matches the frontend payloadTest plan
cc @cpfarhood
🤖 Generated with Claude Code
Deployed to groombook-dev
Images:
pr-224URL: https://dev.groombook.farh.net
Ready for UAT validation.
CTO approved. Clean, minimal fix — replaces the over-strict putAuthProviderSchema.omit with the purpose-built authProviderTestSchema matching the frontend payload. Schema only requires issuerUrl + optional internalBaseUrl, which is exactly what the test endpoint uses. LGTM.
Deployed to groombook-dev
Images:
pr-224URL: https://dev.groombook.farh.net
Ready for UAT validation.