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

[FEAT] Allow 2sxc permissions to work with names instead of IDs #3572

Open
enfJoao opened this issue Feb 9, 2025 · 3 comments
Open

[FEAT] Allow 2sxc permissions to work with names instead of IDs #3572

enfJoao opened this issue Feb 9, 2025 · 3 comments

Comments

@enfJoao
Copy link

enfJoao commented Feb 9, 2025

This Feature is About

[x] edit experience / UI
[x] admin experience UI
[x] Content Types or data management

Feature request

Is your feature request related to a problem? Please describe.
2sxc permission system works with IDs only (users and roles). This even requires a sql query for roles to get the ID.
If you move the app to another install with the same roles, you will need to update all permissions to the new IDs.

Describe the solution you'd like
Work with permissions by user name and role name.
Even better, create a selection for user and roles, like the native DNN ones.

@jeremy-farrance
Copy link

In DNN v9.13.05+, the Role ID was added to the PersonaBar Manage/Roles panel. Screenshot below. I hope this helps.

Also, since Role Names can be changed, simply put, Role ID is the only reliable choice.

Image

@enfJoao
Copy link
Author

enfJoao commented Feb 11, 2025

@jeremy-farrance It helps, yes. But my does not solve my use case.

Imagine this scenario:
I have a rather large app with permissions set for dozens of content items, views, queries, etc. These are set by role id.

Now I need to migrate this app into a new install, freshly setup. Everything will work except for roles, since the role ids will be different on the new install. But the name will be the same since I will set it manually.

@iJungleboy
Copy link
Contributor

I understand the need.
ATM we don't have the resources for it, but I'll leave the task open for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants