Skip to content

Commit f5a3de6

Browse files
committed
chore(sso): tighten the re-grant rationale comment
1 parent 97161ec commit f5a3de6

1 file changed

Lines changed: 3 additions & 5 deletions

File tree

  • apps/sim/app/api/organizations/[id]/domains/[domainId]/verify

apps/sim/app/api/organizations/[id]/domains/[domainId]/verify/route.ts

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -171,11 +171,9 @@ export const POST = withRouteHandler(
171171
.where(and(eq(ssoDomain.id, domainId), eq(ssoDomain.organizationId, organizationId)))
172172
.limit(1)
173173
if (current?.status === 'verified') {
174-
// Re-grant rather than returning early. A provider can hold a verified
175-
// domain while its own trust flag is off — an update whose grant was
176-
// refused reverts to the previous config and clears it. Re-running
177-
// verification is the obvious way to fix that, so it must actually do
178-
// something; the proof is present, which is exactly what authorizes this.
174+
// Re-grant rather than returning early: a provider can hold a verified
175+
// domain with its own flag off, after an update whose grant was refused
176+
// reverted the config. The proof is present, which authorizes this.
179177
await db
180178
.update(ssoProvider)
181179
.set({ domainVerified: true })

0 commit comments

Comments
 (0)