-
Notifications
You must be signed in to change notification settings - Fork 3
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
Terminology Update, Security Considerations, and Example #23
Conversation
|
||
<t> Checklist information, while typically shared publicly, can have potential security impact | ||
if compromised. In these cases, the utmost care should be taken to secure the REST endpoint. | ||
Ensure that only authenticated users can allowed request access to any part of the ROLIE |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can allowed request
?
if compromised. In these cases, the utmost care should be taken to secure the REST endpoint. | ||
Ensure that only authenticated users can allowed request access to any part of the ROLIE | ||
repository. Authentication schemes such as OAUTH or basic HTTP Auth provide a signifigant | ||
barrier to comprimise. When providing checklist information as a paid service, security is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
comprimise
should be compromise
<entry xmlns="http://www.w3.org/2005/Atom" | ||
xmlns:rolie="urn:ietf:params:xml:ns:rolie-1.0"> | ||
<id>6e9b58c5-84eb-491b-b384-4b3425e5f66e</id> | ||
<title>Sample Checlist</title> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Checlist should be Checklist
Closes #21 , starts on #14 , continues #13