Administration Area #116

Closed
opened 2020-08-17 14:12:41 +00:00 by MrLyallCSIT · 8 comments
MrLyallCSIT commented 2020-08-17 14:12:41 +00:00 (Migrated from github.com)

Is your feature request related to a problem? Please describe.
Admins need to be able to view, open, close, assign and update tickets

Describe the solution you'd like
A dashboard similar to the main app designed for admins. Possible in /admin/

Describe alternatives you've considered
Admins access the ticket in phpnyadmin

**Is your feature request related to a problem? Please describe.** Admins need to be able to view, open, close, assign and update tickets **Describe the solution you'd like** A dashboard similar to the main app designed for admins. Possible in /admin/ **Describe alternatives you've considered** Admins access the ticket in phpnyadmin
github-actions[bot] commented 2020-08-17 14:13:09 +00:00 (Migrated from github.com)

Branch 116 created!

Branch [116](https://github.com/luketainton/FHeD/tree/116) created!
MrLyallCSIT commented 2020-09-01 01:29:32 +00:00 (Migrated from github.com)

@luketainton how do we know the user is admin? I can't find anything in the db. Is it set in Keycloak?

@luketainton how do we know the user is admin? I can't find anything in the db. Is it set in Keycloak?
luketainton commented 2020-09-05 15:56:56 +00:00 (Migrated from github.com)

Right now there's nothing to dictate their role - we could have Keycloak push it down through roles, which is probably better than storing it in a db

Right now there's nothing to dictate their role - we could have Keycloak push it down through roles, which is probably better than storing it in a db
MrLyallCSIT commented 2020-09-05 15:59:25 +00:00 (Migrated from github.com)

What if we had keycloak push it down then it gets stored/updated in the DB upon login? That would make the code i have just written work

What if we had keycloak push it down then it gets stored/updated in the DB upon login? That would make the code i have just written work
luketainton commented 2020-09-05 16:11:49 +00:00 (Migrated from github.com)

What if we had keycloak push it down then it gets stored/updated in the DB upon login? That would make the code i have just written work

Keycloak is now configured to push an attribute called roles, which will be set to either admin, agent, or user depending on the desired functionality for the user.

> What if we had keycloak push it down then it gets stored/updated in the DB upon login? That would make the code i have just written work Keycloak is now configured to push an attribute called `roles`, which will be set to either `admin`, `agent`, or `user` depending on the desired functionality for the user.
MrLyallCSIT commented 2020-09-05 16:17:24 +00:00 (Migrated from github.com)

What if we had keycloak push it down then it gets stored/updated in the DB upon login? That would make the code i have just written work

Keycloak is now configured to push an attribute called roles, which will be set to either admin, agent, or user depending on the desired functionality for the user.

I will update the db(s) and creation script. Then update my code accordingly. Also, I was thinking admin and agent are the same thing?

> > What if we had keycloak push it down then it gets stored/updated in the DB upon login? That would make the code i have just written work > > Keycloak is now configured to push an attribute called `roles`, which will be set to either `admin`, `agent`, or `user` depending on the desired functionality for the user. I will update the db(s) and creation script. Then update my code accordingly. Also, I was thinking admin and agent are the same thing?
luketainton commented 2020-09-05 16:19:17 +00:00 (Migrated from github.com)

OK, I'll remove admin. The functions in app_functions.php also need to be updated to a) get the role from KC, and b) save it in the session

OK, I'll remove `admin`. The functions in app_functions.php also need to be updated to a) get the role from KC, and b) save it in the session
github-actions[bot] commented 2020-11-05 00:21:51 +00:00 (Migrated from github.com)

This issue has been marked as stale due to inactivity. If this issue is still ongoing, please leave a comment.

This issue has been marked as stale due to inactivity. If this issue is still ongoing, please leave a comment.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: archives/FHeD#116