[
https://issues.apache.org/jira/browse/JS2-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ate Douma resolved JS2-382.
---------------------------
Resolution: Fixed
I'm resolving this one again as already been resolved.
I cannot reproduce with Tomcat.
There *might* be a problem on other application servers *if* using
JAAS/container authentication when the container is not providing (or allowing
to) principal instances implementing the Jetspeed UserPricipal,RolePrincipal
and GroupPrincipal interfaces.
However this is how the Jetspeed security system works.
For JBoss this *is* possible to configure right, for WebLogic I don't know.
But it is always possible to workaround all this by using PortalFilter based
security integration where you can setup (wrap/inject) this appropriate as
needed for Jetspeed.
> HTTP Status 403 - SecurityConstraintsImpl.checkConstraints(): Access for view
> not permitted
> -------------------------------------------------------------------------------------------
>
> Key: JS2-382
> URL: https://issues.apache.org/jira/browse/JS2-382
> Project: Jetspeed 2
> Issue Type: Bug
> Affects Versions: 2.1.3
> Environment: jboss(3.2.5)4.0.2. jetspeed2-M3 .windows xp
> Reporter: lisheng
> Fix For: 2.1.4
>
>
> I have deployed jetspeed2-M3 on jboss(3.2.5)4.0.2. I use admin(user) login
> ,changing a portlet location or adding a portlet with tool. When I
> restart jboss, the erroe on the browser is:HTTP Status 403 -
> SecurityConstraintsImpl.checkConstraints(): Access for view not permitted,
> Access to the specified resource (SecurityConstraintsImpl.checkConstraints():
> Access for view not permitted.) has been forbidden.
> Can you give me some helps?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
