Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancement/rebase supabase #6

Open
wants to merge 114 commits into
base: master
Choose a base branch
from
Open

Conversation

dpatsora
Copy link
Member

No description provided.

HarryET and others added 30 commits February 26, 2022 14:35
This allows referencing of query parameters when constructing new
provider objects.
This module can be used to easily convert interfaces to structs without
going through the JSON serialization/deserialization dance.
The `provider` query provider is already passed to the `/authorize`
route, so an alternative query parameter (`workos_provider`) is chosen
instead.
… `avatar`

Certain providers (eg. WorkOS, Azure) do not return an avatar URL in
their user profile data. Hence, it is possible for
`user.UserMetaData["avatar_url"]` to be `nil`. However, the
`assertAuthorizationSuccess` function only accepts a `string` to compare
against the stored avatar URL in a test, causing certain tests to fail
when a

This PR tweaks the test for avatar URL to check for `nil` if the
supplied expected input is `""` (the empty string). Various tests are
also modified for the Azure provider, which previously had workarounds
including already creating a user before the signup occurred, which
meant the initial login flow wasn't thoroughly tested.

The alternative would be to change the type of `avatar` to `*string`,
which is a lot more troublesome to write for in the common case of
having an avatar URL, since you can't use the `&` referencing syntax for
string constants.
…st (supabase#408)

* fix: check if current email exists before sending

* refactor: create MailClient interface to mock mail method

* refactor: merge sendEmailChange & sendSecureEmailChange methods

* fix: allow single confirmation if current email doesn't exist

* test: add update user email tests

* add test for UserGet
* Keycloak OAuth Provider

* Update README.md

* Removed the usage of chooseHost to keep things clear

* Allow to use the Keyloak provider in an ID Token grant flow

* fix tests

Co-authored-by: Kang Ming <[email protected]>
* fix: no longer hardcode username for migration

The username is configurable via the connstring, and as such we can't
rely on it being supabase_auth_admin

* update idle transaction timeout time

Co-authored-by: Kang Ming <[email protected]>
* refactor: sendPhoneConfirmation should accept an otpType and smsProvider

* fix: allow update phone for users endpoint

* fix: add phone change verification method
…upabase#424)

This aligns the connection handling behaviour with the rest of the
functions in `api/verify.go`.

This looks like it might have been a leftover bug during refactoring in
PR supabase#379.
darora and others added 29 commits June 14, 2022 18:36
This allows [automated] migrations activity to be differentiated from
user-initiated activity.
* fix: add captcha to verify and token endpoints

* don't enable captcha on refresh token grant_type

* refactor: rename hcaptcha_token to captcha_token for generalizability
Keycloak URL is not included /auth/ after hostname. Readme file and description has a mistake.
Edit Keycloak OpenID endpoint url
* fix: add migrations to hash email

* add email otp length to config

* remove email hash migration

* send email hash & otp in email link

* verify post should check for token hash

* fix verify tests

* fix tests

* update generate_link endpoint

* remove magic number

* use sum224 instead of md5
* Upgrade Kaigara to version 0.1.34

Co-authored-by: Anton Filonenko <[email protected]>
@dpatsora dpatsora force-pushed the enhancement/rebase-supabase branch from 0a71696 to f943b0f Compare July 11, 2022 05:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.