Skip to content

Correct out-of-date roles info in README #310

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.

Sign up for GitHub

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

Merged
JohnKallies merged 1 commit into from
Feb 14, 2023
Merged

Correct out-of-date roles info in README #310

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -194,13 +194,13 @@ osmt_cli.sh -m
* Keep in mind that removing Docker volumes will also remove this metadata. For more information, see the section for [Importing Data](api/README.md#importing-data) in the API README file.

### Role-based Access in OSMT
* Role-based access is **enabled** by default for the Angular UI and Spring REST API.

OSMT optionally supports role-based access, with these roles:
- **Admin**: an OSMT user with an admin role can change RSDs and Collections in any way.
- **Curator**: an OSMT user with a curator role can update but not create RSDs and collections. This role is for someone who would publish and unpublish RSDs and Collections
- **Viewer**: an OSMT user with a viewer role is a logged-in user who can not make modifications to RSDs or Collections.

Role-based access is disabled by default for the Angular UI and Spring REST API. Use these steps to enable roles.

#### Configuration in OSMT Code
By default, OSMT is configured with roles enabled. If you want to disable roles in OSMT, apply these changes:

Expand Down