Stojan Dimitrovski

icon indicating a website link https://stojan.me icon indicating an email [email protected]

icon company @supabase icon location Skopje, Republic of North Macedonia icon location Craftsman of bits and bytes.

Results 213 comments of Stojan Dimitrovski

Create a `supabase.auth.admin.getUserByEmail` function

Hey yes this is a good suggestion. Though, we would probably use something like `listIdentitiesForEmailAddress` since email addresses do not always uniquely identify users.

Updating the asymmetric signature recommendations

@zekth Yes I agree with the JWK approach as I raised it previously too -- IMO we're bound to end up either using it or reinventing it. In general my...

Updating the asymmetric signature recommendations

> The content to be signed is still: {msg_id}.{timestamp}.{payload}. This in now HMAC256 with the consumer id (discussed above) instead of with the secret (done in the symmetric case), and...

Updating the asymmetric signature recommendations

> Do we want to propagate in the header some informations regarding the publickey or should it be defined by the spec from the producer? It's always a good idea...

"supabase.auth.getUser()" is returning a null user value in nextjs middleware.ts using @supabase/supabase-js @supabase/ssr only

> somoeone suggested the set method is only setting one cookie at a time... This could very well be the case. We're about to release 0.4.0 of `@supabase/ssr` in the...

SAML Metadata parsing does not correctly parse valid duration values.

Looks like this is a bug in the underlying library, the `EntityDescriptor` type correctly parses the `Duration` but not the `EntitiesDescriptor` (plural!): https://github.com/crewjam/saml/blob/main/metadata.go#L30-L103 Will take a while to fix given...

SAML Metadata parsing does not correctly parse valid duration values.

Proposed a fix: https://github.com/crewjam/saml/pull/575

SAML Metadata parsing does not correctly parse valid duration values.

If we don't see any movement on this in the library, the only option we have is to essentially fork.

fix: add support for migration of scrypt passwords

Would prefer if the name for the Firebase scrypt be `fbscrypt` instead of `scrypt`.

feat: MFA (WebAuthn)

Let's rename the title to WebAuthn, not FIDO2.