ENG-2519: Additional SSO Configuration#7351
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
d6706cf to
8d912a1
Compare
35e741e to
9e38fbc
Compare
Greptile OverviewGreptile SummaryThis PR adds additional SSO configuration options for custom OpenID providers, including scopes, email field mappings, and email verification settings. Key Changes:
Issues Found:
Confidence Score: 3/5
Important Files Changed
|
...alembic/migrations/versions/xx_2026_02_10_1850_4d64174f422e_additional_sso_configurations.py
Outdated
Show resolved
Hide resolved
...lembic/migrations/versions/xx_2026_02_10_1850_4d64174f422e_additional_cors_configurations.py
Outdated
Show resolved
Hide resolved
Additional Comments (1)
|
|
@greptileai pls rereview |
clients/admin-ui/src/features/openid-authentication/SSOProviderForm.tsx
Outdated
Show resolved
Hide resolved
|
@greptileai pls rereview |
| domain?: string | null; | ||
| scopes?: Array<string> | null; | ||
| email_field?: string | null; | ||
| verify_email?: boolean | null; |
There was a problem hiding this comment.
Type mismatch: verify_email is defined as nullable here but the backend model has nullable=False. This could cause runtime errors if the frontend sends null. Since these are auto-generated files, check the backend API schema generation to ensure it correctly reflects nullable=False.
There was a problem hiding this comment.
I'll try it but this should be fine given that the database has a default value.
lucanovera
left a comment
There was a problem hiding this comment.
Tested UI with the new array interface, add/edit/save works correctly. approved
|
@tvandort I noticed when you edit a provider, the client id and secret fields are empty but marked as required so you can't save until you enter those again. I'm not sure if the api supports partial updates or not, in any case it can be a followup improvement |
|
Migration/BE model looks good - I have not tested. |
b8c1605 to
fc23a8b
Compare
@lucanovera I didn't see this before but I believe this is by design. If you were able to change the authorization endpoint without re-entering the client id and client secret you a malicious administrator could redirect the auth flow to a malicious server and receive the id and secret. Could be wrong but it reads to me like a feature not a bug. |


Ticket ENG-2519
Description Of Changes
Allows further SSO configuration including scopes, fields, verification toggle.
Steps to Confirm
Pre-Merge Checklist
CHANGELOG.mdupdatedmaindowngrade()migration is correct and works