[jira] Updated: (COUCHDB-441) Finally implement pre-write-doc-edit handlers.

["Paul Joseph Davis (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/COUCHDB-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Joseph Davis updated COUCHDB-441:
--------------------------------------

          Component/s:     (was: Database Core)
                       HTTP Interface
    Affects Version/s: 0.10
             Assignee:     (was: Paul Joseph Davis)
              Summary: Finally implement pre-write-doc-edit handlers.  (was: Mechanism for inserting user from user_ctx into documents on writes )

Renamed before I forget what the other title means.

> Finally implement pre-write-doc-edit handlers.
> ----------------------------------------------
>
>                 Key: COUCHDB-441
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-441
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: HTTP Interface
>    Affects Versions: 0.10
>            Reporter: Curt Arnold
>             Fix For: 0.10
>
>
> It would be useful for auditing to have the identity of the user who inserted a new revision and the timestamp of the operation to be inserted in the document in the same way that the new revision number is.
> Doing this at the application level is not adequate since it would be readily spoofable and would bypass the authentication handler.
> There is a comment in couch_db:update_docs about generating new revision ids, but I couldn't quite comprehend what specific code was responsible for inserting the id into the document.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.