Github user kxepal commented on the pull request:
https://github.com/apache/couchdb/pull/366#issuecomment-155252688
@KlausTrainer Well, if I gave someone auth_token for my CouchDB and this
someone started to do bad things there, I would like to make sure I can ban
him. Yes, I can do that on my third party app side which runs delegated auth,
but until he hold auth_token cookie and it's not expired he is still an active
user for CouchDB.
JWT support indeed would be nice. Not only as delegated auth, but as
alternative to cookie one (because for some cases auth cookies are hard). But
indeed, we need to finish blockers and broken compatibility issues first.
However, if we can do both - that would be awesome (:
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
