Test sign-in
Before you publish, sign in with your own account. Gephyr runs three checks, and you can publish once all three pass.
| Check | What it proves |
|---|---|
| Signed in as you | Gephyr confirmed who signed in, using a stable account ID from your provider (shown shortened) |
| Real API call works | One of your read actions ran against your API as you, and your API accepted the token |
| Token refresh works | Gephyr refreshed your session and the new token works too, so users stay connected |
If a check fails
Each failure names the broken part. The common ones:
| Message | Fix |
|---|---|
| Your sign-in server rejected Gephyr’s client credentials | Check the client ID and secret, or Connect again. |
| Couldn’t confirm your account | For OpenID providers, make sure the openid scope is allowed. For “identity endpoint” setups, check the address returns the user and the ID field is right. |
| Your API rejected the signed-in user’s token | Your API must accept tokens from this sign-in. Auth0: set the audience to your API’s identifier. Firebase/Supabase: your API must verify that provider’s tokens. |
| Your sign-in server didn’t issue a refresh token | Allow offline_access (or your provider’s equivalent) and enable refresh tokens for the Gephyr app. In Auth0, also turn on Allow Offline Access for your API. |
| This client is not allowed to use refresh tokens | Enable the refresh token grant for the Gephyr app. |
| The token URL could not be reached | Check the address is correct and publicly reachable over HTTPS. |
| This account uses two-step verification… | Firebase/Supabase direct sign-in only: test with an account without two-step verification, or switch to an OAuth provider setup. |
| No action to test | Publish at least one read action that uses the signed-in account and needs no inputs. |
Still stuck? Use Ask your AI to help. It gives your own assistant everything we found and the exact error, but never your secrets.
Something missing or wrong? Email hello@gephyr.ai.