Open Source Document Management System | OpenKM

Hi,

What causes this issue?
HTTP Status 403 - Access to the requested resource has been denied

type Status report

message Access to the requested resource has been denied

description Access to the specified resource (Access to the requested resource has been denied) has been forbidden.
JBossWeb/2.0.1.GA

I saw an old post but it seems the issue was fixed...
http://forum.openkm.com/viewtopic.php?f=3&t=3446

I got to this issue by creating a new user, giving him a user role that i made with the UserRole(default role) assigning the default profile...
I granted this user permissions to the okm:root and a sub folder as well.

could you describe exactly the sequential operations to reproduce it ? and which openkm version are you using ?

OKM Version 5.1.9 [latest ]

Steps done:
Make user test
Assign Roles UserRole & Misc
Assign Default profile
test user was given permissions for the root folder without recursive permission.
test user was given to a misc folder with recursive permission.
login error

Setup of okm:
User role (not UserRole) has read and write permissions
Every specific user has read and write permissions (roles dont seem to work for me atm)
UserRole cannot be found in the list of roles (this happened after the first test system crashed and was recovered)

problem solved... i did no other change, last i was seeing was the error, i posted on the forum and went home for the day. I came back just now to document the steps and see that the test user can login fine...
cause unknown...

First time you created the user, has forget some role, then have you tryed to login and get that error, after it you have loged with administrator added the role but seems the user continues presenting the same error ... could it be the scenario ? I said it because there is a problem with jboss security cache that after a login seems continues having initial values and not refreshing ( sometimes needs some minutes for reflexting some changes ).

you are correct!
After a day the cache must of auto cleared and thus problem solved