The top-level superproject for zLUX. zLUX includes the Zowe Desktop framework in addition to several built-in apps and an example server implementation.
Eclipse Public License 2.0
39
stars
42
forks
source link
RBAC: Always use userid in CAPS when checking for applications the user has access to #861
We are using RBAC to control access to some applications for individual users. When a user logs on for the first time, Zowe creates a directory in '/workspace/app-server/users' directory for the user in CAPS (e.g. when I log on as 'buddy' to Zowe, I get a directory 'BUDDY' in Unix System Services).
After editing allowed Plugins.json for Buddy and restarting Zowe, Buddy logs on to Zowe again as 'buddy'. But the granted application does not show in the application menu of Zowe desktop. But when he logs on as 'BUDDY' to Zowe, the application shows up in the menu.
Zowe should always use User-ID in CAPS when checking for access to applications.
We are using RBAC to control access to some applications for individual users. When a user logs on for the first time, Zowe creates a directory in '/workspace/app-server/users' directory for the user in CAPS (e.g. when I log on as 'buddy' to Zowe, I get a directory 'BUDDY' in Unix System Services). After editing allowed Plugins.json for Buddy and restarting Zowe, Buddy logs on to Zowe again as 'buddy'. But the granted application does not show in the application menu of Zowe desktop. But when he logs on as 'BUDDY' to Zowe, the application shows up in the menu.
Zowe should always use User-ID in CAPS when checking for access to applications.