-
Notifications
You must be signed in to change notification settings - Fork 251
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
Feature request: roles management (multi-profile) #24
Comments
What is the purpose of that? |
To be more granular. If your app has x group of users and you want to give different rights, for example :
(by default, the actual case, user has all roles ) |
I see now, may be interesting feature. |
Yes, I will do that but before I would like:
|
Of course if you both work on the same connector. |
Connectors are very close, but I can't use the @gmkll without modifications. I will open |
That's would be great. |
I have a similar need that I will be implementing into my node connector. In my case, I need to block access to files based upon user roles. So my root folder will have folders for each role, and each request will verify that the user has the role that matches the folders name or they will be denied. This way I can have groups that have private files. I will write it in such a way that it can be easily ignored, aka, opt-in. Node uses a standard user configuration that roles can be added to, I'm not sure how it would work in other connectors except .net. I did this to my current .net connector, but it was horribly messy and non-standard so I never even thought about passing it back as a pull request. My node connector I will, though. I will go to lengths to make it standard compliant and clean. |
Solved with the RichFilemanager release v2.0.0 |
@fabriceci @servocoder is it possible to do to give different rights to user, admin or superadmin,.. with filemanajer.js node connector? |
I think it will be nice to have a simple roles management.
Suggestion:
We can add a new constructor with an array of roles as extra parameters. By default, if nothing is provided (actual case) a user has all roles.
When the file manager start, it does an extra request to get the user roles to the connector. (It does not seem too hard to implement because the logic is already implemented with the "has_capability" functions.)
This will real plus in a CMS usage or when you have different profiles of users that use the file manager in your app.
The text was updated successfully, but these errors were encountered: