Missing Roles in DB

121 views
Skip to first unread message

Tim Walls

unread,
Sep 9, 2021, 9:44:54 PM9/9/21
to Unified-RED
Hi, not sure if roles is implemented or not yet.
But performed fresh install on fresh NodeRed install using SQLITE DB.

In the interface the user roles page is empty
In the user management the role column is empty.
If I try to create a new user, I am unable to select any roles.

Checked the SQLITE DB and found that the roles table is empty.
Checked the user account already created in the DB and confirmed role: 10



Samy Arbid

unread,
Sep 11, 2021, 1:23:32 PM9/11/21
to Unified-RED
Hi Tim,

Roles are implemented and if they don’t exist, they are created on startup. If you launch node-red and the roles are not created, we have a bug. If you have a GitHub account, would you be able to open a new bug report? https://github.com/waccit/unified-red/issues We’ll track the issue and you’ll be notified automatically when a fix is released.

If you don’t have a GitHub account, please reply with the following information. The environment and context information will be very important for us to reproduce the issue.

**Describe the bug**
A clear and concise description of what the bug is.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Affected Environment (please select one or more):**
[ ] Node-RED
[ ] Unified-RED
[ ] Backend

**Context:**
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.
* Operating System: 
* Node.js version: 
* npm version: 
* Node-RED version: 
* Unified-RED version: 

**Additional context**
Add any other context about the problem here.

Tim Walls

unread,
Sep 12, 2021, 7:30:55 PM9/12/21
to Unified-RED
Hi,

Issue appears to have resolved itself, so maybe resolved with a restart or browser cache clear.
Thanks for the info.

Reply all
Reply to author
Forward
0 new messages