S
Supabase•2h ago
keru

Why dont I have a current key?

Why don't I have a current JWT Signing key? I'm not sure if this is the reason but when signing a user in with the following client: 
object SupabaseClient {
    val client = createSupabaseClient(
        supabaseUrl = "https://[REDACTED].supabase.co",
        supabaseKey = "sb_publishable_[REDACTED]"
    ) {
        install(Auth) {
            flowType = FlowType.PKCE
            scheme = "[REDACTED]"
            host = "auth"
        }
    }
}
object SupabaseClient {
    val client = createSupabaseClient(
        supabaseUrl = "https://[REDACTED].supabase.co",
        supabaseKey = "sb_publishable_[REDACTED]"
    ) {
        install(Auth) {
            flowType = FlowType.PKCE
            scheme = "[REDACTED]"
            host = "auth"
        }
    }
}
the currentAccessTokenOrNull() returns an older HS256 symmetric secret instead of the new ES256 keys which i want to verify on a REST-API with the well-known file. Can it be because i dont have a current JWT Signing key? or is there a different issue happening here
No description
0 Replies
No replies yetBe the first to reply to this messageJoin

Did you find this page helpful?