[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: PASOE - Programmatically access ACLs

Status
Not open for further replies.
J

jmls

Guest
sure, we'll keep you in the loop, Depending on how your apis are constructed, you could use the paths and the verbs to define the permissions for the front end. For example if the csv dictates that POST /users A,B,C PUT /users/:id A,B,C GET /users A,B,C,D DELETE /users A you can say to the front end that users in groups A,B,C have CREATE. UPDATE and READ permissions , only group D can DELETE users and group D have read-only permissions As Tomcat can be configured to read files from anywhere on disk and serve them on a specific URL, create a url to return the csv file from the tomcat config folder to the client, which can parse the csv file and apply it to the front end routing. If you're using angular, you can define the routes to be the same as the backend api , and add guards to check that the user has the right permissions to access that particular route

Continue reading...
 
Status
Not open for further replies.
Top