You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, only the legacy v1 Scope or the token-based Authenticate is supported, but no SignIn with Access is supported.
The v0.2.1 allowed direct access to the underlying Gorilla Websocket, so that allowed for a workaround (sending the signin ourselves), but v0.3.0 does not expose that connection. The .Query function filtering for a whitelist of allowed methods makes a workaround for v0.3.0 impossible.
Steps to reproduce
N/A
Expected behaviour
To have any way to sign in using ACCESS.
SurrealDB version
surreal 2.0.4 for linux on x86_64 with surrealdb.go v0.3.0
Contact Details
No response
Is there an existing issue for this?
I have searched the existing issues
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently, only the legacy v1
Scope
or the token-basedAuthenticate
is supported, but noSignIn
with Access is supported.The v0.2.1 allowed direct access to the underlying Gorilla Websocket, so that allowed for a workaround (sending the signin ourselves), but v0.3.0 does not expose that connection. The
.Query
function filtering for a whitelist of allowed methods makes a workaround for v0.3.0 impossible.Steps to reproduce
N/A
Expected behaviour
To have any way to sign in using ACCESS.
SurrealDB version
surreal 2.0.4 for linux on x86_64 with surrealdb.go v0.3.0
Contact Details
No response
Is there an existing issue for this?
Code of Conduct
The text was updated successfully, but these errors were encountered: