longaccess/longaccess-docs

Longaccess developers documentation

longaccess-docs

This is the Longaccess developers documentation.

This document is located at http://github.com/longaccess/longaccess-docs

• If you are not familiar with longaccess, you should read What is Longaccess?.
• The Introduction to Longaccess API is a higher-level overview of how the longaccess API works.
• The api folder has an extensive and detailed information about the API.

For questions or suggestions, join us at the Longaccess Developers Community on Google+.

You can also keep up with the Longaccess Development Team at longaccess.io

history

To view older versions of some of the files in this repo do:

git remote add history [email protected]:longaccess/longaccess-cli.git
git fetch history docs:docs
git replace 3d9b15fc4f92936ad3aeb0732f31f1ef6c2d2376 36ee0389f22ea082e894d6f795e4dee49f207790

longaccess-docs's Issues

move creator info to Signature or Certificate

this data is overriden by the server, we shouldn't create it in the Archive/Meta area.

add archive creation/expiration date to signature

the signature document should contain the creation and expiration date as returned by the API. Currently we only save the date the user created the archive in the Archive.meta document.

test moving repo to organization

test it

api makes it difficult to find out who uploaded an archive

As it is, an archive resource can tell us the capsule but the capsule resource doesn't expose the user id.

Also, if the capsule-archive relationship is many-to-one then the archive will have to expose a list of capsules, or nothing.

Server-side decryption API resource

Document this feature when implemented.

document the archive expiration and URI attributes in upload response

We should document the response attribute for archive expiration, i.e. what will go on the certificate.

update json returns to latest api

@comzeradd json returns need updating in capsule and archive sections.