Issue Details (XML | Word | Printable)

Key: JS2-206
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: niranjan
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Jetspeed 2

Gives the error as Access to the specified resource (SecurityConstraintsImpl.checkConstraints(): Access for view not permitted.) has been forbidden. when logged in as admin, in jboss 3.2.6

Created: 07/Feb/05 06:35 PM   Updated: 18/May/05 06:13 PM
Component/s: None
Affects Version/s: 2.0-M1
Fix Version/s: 2.0-dev/cvs, 2.0-M2

Time Tracking:
Not Specified

Environment:
windows 2000
Jboss 3.2.6
j2sdk 1.4.2_07

Resolution Date: 02/Apr/05 12:35 AM


 Description  « Hide
I have deployed Jetspeed 2.0 in JBoss 3.2.6.
I tried to login using the admin or any other role.
But who ever logs in the following error is shown


SecurityConstraintsImpl.checkConstraints(): Access for view not permitted.

Access to the specified resource (SecurityConstraintsImpl.checkConstraints(): Access for view not permitted.) has been forbidden.

I have checked the below files too, and every thing seems to be fine.

1. Global: As declarations in the page.security file found in the root of the PSML tree.
2. Folder: In the folder.metadata file optionally located in every directory
3. Page: In PSML files to constraint access to specific pages





 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Randy Watler added a comment - 07/Feb/05 11:39 PM
Please attach a copy of jetspeed.log to this issue to help us narrow down potential causes. The jetspeed.log file can be found in webapps/jetspped/logs. Also, please mention any edits to jetspeed-spring.xml.

Ate Douma added a comment - 02/Apr/05 12:35 AM
I've tested this with the current Jetspeed-2 cvs head version on JBoss 3.2.7 with no problem.
Although this might not be working with the JS2-M1 release, it seems to be resolved now
(and a new JS2-M2 release can be expected very soon now...)

Jian Liao added a comment - 18/May/05 06:13 PM
Hi all,
I encountered the same problem in Tomcat 5.0.30 and JDK 1.4.2_07. It seems like recreate database can fix it. I still don't know the reason, but it works.

Jian Liao added a comment - 18/May/05 06:13 PM
Hi all,
I encountered the same problem in Tomcat 5.0.30 and JDK 1.4.2_07. It seems like recreate database can fix it. I still don't know the reason, but it works.

My j2 version is the newest JS2-M3