S
Supabase•2mo ago
nikkinikk

Migrating from anon > publishable key supabase JS

Hello! Im trying to replace my anon key with the new publishable key in supabase JS client and the new key is not being accepted. The Supabase API Gateway logs are giving me a "bad_length" error - any ideas on why this could be the case?
4 Replies
ihm40
ihm40•2mo ago
Worth trying to isolate the issue so could you try using the old anon key and see what the APi gateway logs give. I imagine if you looked in the console you should get some 401 or something along those lines
nikkinikk
nikkinikkOP•2mo ago
yes! anon key logs: 
            "jwt": [
                {
                  "apikey": [
                    {
                      "invalid": null,
                      "payload": [
                        {
                          "algorithm": "HS256",
                          "expires_at": 2062647862,
                          "issuer": "supabase",
                          "role": "anon",
                          "signature_prefix": "XXXXXX",
                          "subject": null
                        }
                      ]
                    }
                  ],
            "jwt": [
                {
                  "apikey": [
                    {
                      "invalid": null,
                      "payload": [
                        {
                          "algorithm": "HS256",
                          "expires_at": 2062647862,
                          "issuer": "supabase",
                          "role": "anon",
                          "signature_prefix": "XXXXXX",
                          "subject": null
                        }
                      ]
                    }
                  ],
publishable key logs: 
          "sb": [
            {
              "apikey": [
                {
                  "apikey": [
                    {
                      "hash": null,
                      "prefix": "sb_publishable_XXXXX"
                    }
                  ],
                  "authorization": [
                    {
                      "error": "bad_length",
                      "hash": null,
                      "prefix": "sb_publishable_X"
                    }
                  ]
                }
              ],
              "auth_user": null,
              "jwt": []
            }
          ],
          "sb": [
            {
              "apikey": [
                {
                  "apikey": [
                    {
                      "hash": null,
                      "prefix": "sb_publishable_XXXXX"
                    }
                  ],
                  "authorization": [
                    {
                      "error": "bad_length",
                      "hash": null,
                      "prefix": "sb_publishable_X"
                    }
                  ]
                }
              ],
              "auth_user": null,
              "jwt": []
            }
          ],
received a 401 from POST /auth/v1/token with the new publishabl ekey
garyaustin
garyaustin•2mo ago
So I get that error if I delete or add an extra character from my publishable key. Seems like you are not using the right key or are adding/missing letter.
nikkinikk
nikkinikkOP•2mo ago
@garyaustin omg...I swear to god i was clicking the clipboard icon to copy, and somehow just saw there was a random backslash that was getting intot he middle of the string... that fixed it - thank you very much for the nudge to look closely at the string!! have no idea how that happened

Did you find this page helpful?