Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to allow any database member to write revisions for a specific document type #2

Closed
OldSneerJaw opened this issue Mar 1, 2018 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@OldSneerJaw
Copy link
Owner

OldSneerJaw commented Mar 1, 2018

There are cases where any user, so long as they have provided valid authentication, should be allowed to add, replace or remove documents of a particular type. Provide a document definition configuration option to enable this behaviour on a case-by-case basis for each document type.

For example:

{
  myDocType: {
    typeFilter: ...,
    allowUniversalWriteAccess: true,
    propertyValidators: ...
  }
}

Note: when set to true, this configuration option should override any authorization rules specified by the authorizedRoles and authorizedUsers constraints.

@OldSneerJaw OldSneerJaw added the enhancement New feature or request label Mar 1, 2018
@OldSneerJaw OldSneerJaw self-assigned this Mar 1, 2018
OldSneerJaw added a commit that referenced this issue Mar 1, 2018
In cases where any authenticated user should be allowed to add, replace or remove documents of a particular type, the document definition may now include the `allowUniversalWriteAccess` constraint.
@OldSneerJaw
Copy link
Owner Author

Resolved by commit 05899e0.

@OldSneerJaw OldSneerJaw changed the title Option to allow any authenticated user to write revisions for a specific document type Option to allow any database member to write revisions for a specific document type Mar 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant