mirror of
https://github.com/hanzoai/sign.git
synced 2026-11-02 23:26:15 +00:00
zooqueenandHanzo Dev
ecee5e40aa
The IAM callback at /auth/callback reads IAM's userinfo answer and refuses an address IAM has not verified. An account is found by its linked IAM identity alone (provider hanzo, the IAM subject); an existing account that only shares the address is refused, never merged. A first sign-in makes an account only for an admin of the org the application serves or for someone an organisation invited at that verified address. Every refusal returns to /signin with a sentence saying what to do. Accepting an organisation invitation joins the signed-in person, and only when their verified address is the invited one; opening the link no longer adds whoever holds the address. The local email/password sign-up, sign-in, reset, verify-email and update routes, pages, jobs and mail are gone, as are passkey sign-in, the Google, Microsoft and generic OIDC providers, the per-organisation SSO portal and its account-link flow. Passkeys and two-factor stay for confirming a signature. The e2e suite starts sessions the way a finished IAM sign-in leaves them. Co-authored-by: Hanzo Dev <[email protected]>
13 lines
500 B
TypeScript
13 lines
500 B
TypeScript
/**
|
|
* Whether user is the person an invitation sent to invitedEmail names: their
|
|
* address is verified and is that address. Emails are stored lowercased (see
|
|
* the invite schema), and SQLite has no case-insensitive filter, so both sides
|
|
* are compared lowercased.
|
|
*/
|
|
export const isInvitedPerson = (
|
|
user: { email: string; emailVerified: Date | null },
|
|
invitedEmail: string,
|
|
): boolean => {
|
|
return user.emailVerified !== null && user.email.toLowerCase() === invitedEmail.toLowerCase();
|
|
};
|