snturk / sharky Goto Github PK

README.md file must be created to describe following about Sharky:

• Purpose
• Main Logic
• Principles
• Structure
• Contribution Rules

A object-specific permission check functionality needed.

To achieve that, Sharky needs capability to identify & separate object's by looking into their data such as type or tags.

• It's a possibility to add a field to SharkyObject like objectType or simply type to be able to distinguish objects.
• Another possible solution is adding a string field, when permissions are defined, developer can provide a pattern with its own rules like myObj/not/readable/by/mathcingroles/myRegex

All models, functions and compound functionalities must be tested before project gets complicated.

• A test structure will be created.
• Tests must be written for current state of the project

Sharky store permissions on roles. Each role should contain needed permissions for this role.

Objects also have urn field to distinguish from other objects. In Permission model, URN-Action combination means that "This permission allows {Action} to execute on specified {URN}". This needs to be improved to work in a more secure way.