Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Remove getAccounts and migrate accounts+capabilities to Authentication #58

Open
ddolcimascolo opened this issue Oct 19, 2016 · 1 comment
Open

Remove getAccounts and migrate accounts+capabilities to Authentication #58

ddolcimascolo opened this issue Oct 19, 2016 · 1 comment
Labels
help wanted

Comments

@ddolcimascolo
Copy link
Contributor

As per https://groups.google.com/forum/#!topic/jmap-discuss/9XKdZrp2mBE and http://jmap.io/spec-core.html#getting-an-access-token
@thomascube
Copy link
Contributor

I started working on this

thomascube added a commit to roundcube-next/jmap-client that referenced this issue Oct 3, 2017
@thomascube
Add JSONBuilder.appendObject()
3812ff4 
Will append an object property to the building object by recursively calling toJSONObject() on each own property.

This is a preparation for linagora#58
thomascube added a commit to roundcube-next/jmap-client that referenced this issue Oct 3, 2017
@thomascube
Migrate accounts+capabilities to new JMAP authentication spec
b6eb18b 
According to the recent updates to the JMAP spec, account data is now loaded from the authentication response. Therefore the AuthAccess model was significantly changed to serve as a container for authentication data, account information and server capabilities.

This change requires authentication responses to comply with the latest spec as the model requires certain new properties to be present.

Added: jmap.ServerCapablities
Removed: jmap.AccountCapabilities

The namespace URIs used for the various capabilites are defined in jmap.Constants but not yet final.

see links in issue linagora#58
thomascube added a commit to roundcube-next/jmap-client that referenced this issue Oct 3, 2017
@thomascube
Update Changelog (linagora#58)
4ce2aab
@thomascube thomascube mentioned this issue Oct 9, 2017
Closed
fabienmoyon pushed a commit to fabienmoyon/jmap-client that referenced this issue Oct 13, 2017
@thomascube @fabienmoyon
Add JSONBuilder.appendObject()
19b1b13 
Will append an object property to the building object by recursively calling toJSONObject() on each own property.

This is a preparation for linagora#58
fabienmoyon pushed a commit to fabienmoyon/jmap-client that referenced this issue Oct 13, 2017
@thomascube @fabienmoyon
Migrate accounts+capabilities to new JMAP authentication spec
966c4e7 
According to the recent updates to the JMAP spec, account data is now loaded from the authentication response. Therefore the AuthAccess model was significantly changed to serve as a container for authentication data, account information and server capabilities.

This change requires authentication responses to comply with the latest spec as the model requires certain new properties to be present.

Added: jmap.ServerCapablities
Removed: jmap.AccountCapabilities

The namespace URIs used for the various capabilites are defined in jmap.Constants but not yet final.

see links in issue linagora#58
fabienmoyon pushed a commit to fabienmoyon/jmap-client that referenced this issue Oct 13, 2017
@thomascube @fabienmoyon
Update Changelog (linagora#58)
74219ff
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@thomascube @ddolcimascolo