-
Notifications
You must be signed in to change notification settings - Fork 54
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
feat: use new authentication mechanism (access/refresh token) #663
Comments
This has to be addressed as soon as possible in order for the development environment to work for everyone running If you are in this situation, you can rebuild the docker environment with a JM backend of tag |
|
So, this is generally ready for review. However, I am leaving it in "draft" mode as there is still an upstream problem with wallets that contain whitespaces, see JoinMarket-Org/joinmarket-clientserver#1480 (comment). @roshii I'd highly appreciate if you could take a look. 🙏 |
I'm on it, ready by the end of the week latest. |
Nice. No time specifications required. Absolutely no urgency involved. |
c88429d JWT authority fixes (roshii) Pull request description: - Fix JWT unit tests (`async` was somehow making tests always successful therefore hiding some issues) - Fix `WWW-Authenticate` header construction (#1480 (comment)) - Encode wallet names with base64 in scopes to allow for space delimited names (#1480 (comment), joinmarket-webui/jam#663 (comment)) - Fix syntax errors in OpenAPI RPC documentation (#1559) Top commit has no ACKs. Tree-SHA512: 6625c4c457c4caf3b4979505334c955bec50fcc0b01707e313dc772571c5c8c8b3ca359a18b5e67f1b0d0eb9b2b7c234ae9716d785234e8de0f3bfb76d53d29a
Newest
master
of JM contains changes to the authentication mechanism.See JoinMarket-Org/joinmarket-clientserver#1480 for more information.
From JSON-RPC-API-using-jmwalletd.md#rules-about-making-requests:
The OpenAPI spec can be found in wallet-rpc.yaml.
At the time of writing, this functionality has not been released and will probably land in JM
v0.9.11
.The text was updated successfully, but these errors were encountered: