You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2019/04/01 10:50:56 UTC

[GitHub] [couchdb] janl commented on issue #844: Add new explicit authentication-tokens that can be revoked

janl commented on issue #844: Add new explicit authentication-tokens that can be revoked
URL: https://github.com/apache/couchdb/issues/844#issuecomment-478531126
 
 
   FWIW, I think we can design a new feature here. if we change any existing API’s, we need to run an email + lazy consensus by dev@, but that’s it in terms of process.
   
   What would work best is:
   - agree on semantics for a new session endpoint
   - have a PR that adds that feature
   - ship a 2.x release where people can opt into that new behaviour
   - when 3.x comes out, make the new behaviour the new default and optionally, let folks opt into 2.x and earlier behaviour.
   - in 4.x then, we can remove the old behaviour, if we want

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services