-
Notifications
You must be signed in to change notification settings - Fork 22
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
Activity/maintenance of jmap-client #87
Comments
Hello @jeserkin , I can answer questions on the James side... We did put together work on the James side to implement the newest JMAP specification (RFC-8620 & RFC-8621). While the JMAP drafts did explicitl require a token based authentication (continuation token and authentication token), the new JMAP specification do not. As at Linagora we do use signed JWT tokens to authenticate users, we did not implement some of the mechanisms that were mandated in draft. I think that, on the long term, James would need to comply with some kind of OIDC flow. I imagine it would be relatively easy to backport authentication mechanisms you need to the new version of the RFCs. PRs are welcome for this. |
For your information, I did start a little pull request to better document authentication on top of JMAP RFC-8621: linagora/james-project#4093 |
Hello @jeserkin ! This repository contains our implementation of the draft version of the JMAP protocol. We will not make it support JMAP version 1. We started a new client library in TypeScript here https://github.com/OpenPaaS-Suite/jmap-client-ts . It's an early early release, not even alpha, but of course feel free to take a look ! Regards, Michael |
@MichaelBailly maybe it could be nice to pr the jmap website software implementation page to reflect this? |
@MichaelBailly I see. I was just about to post, that current jmap-client code doesn't support Version 1 standard as far as I can tell. I will look into new jmap-client, that supports TypeScript. This is much more preferable these days. |
@MichaelBailly I made a PR today for https://github.com/OpenPaaS-Suite/jmap-client-ts . Should I notify anyone about it? I see, that there was a second person involved when other PRs were reviewed. |
Thank you very much for your contribution. We got it, the review is on its way. |
Was wondering if given project is still maintained/supported?
Question came up due to last visible changes made 7 month ago.
I have tested it with Apache James and it looks like authorization has changed on Apache James side, but did not change in this library.
I made certain changes in my fork, so that authorization can be used again and can post PR.
The text was updated successfully, but these errors were encountered: