[
https://issues.apache.org/jira/browse/COUCHDB-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769255#action_12769255
]
Paul Joseph Davis commented on COUCHDB-540:
-------------------------------------------
Definitely a valid point. Does the _users database not do what you're needing?
Or is there another method you'd prefer? At one point someone mentioned writing
an ldap connector but I've never heard what happened to that. I'm not sure I
follow about an FHS violation.
Another possibility that was discussed was giving the config writer more smarts
so that it'd remember the last file that defined a section and use that as the
write back target for each section. This would allow you to have a
local_users.ini that would receive updates via config API and not get appended
to some other random file that happened to sort last.
> oauth_token_users seems to be in the wrong place
> ------------------------------------------------
>
> Key: COUCHDB-540
> URL: https://issues.apache.org/jira/browse/COUCHDB-540
> Project: CouchDB
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: 0.10
> Environment: Ubuntu Linux
> Reporter: Chris Jones
>
> If one has many users, the oath_token_users section of /etc/couchdb/local.ini
> becomes quite large. This:
> a) makes legitimate configuration of the server less friendly
> b) makes the file extremely hard to manage via version control
> c) is probably a violation of the FHS.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
