0 Replies Latest reply: Jan 11, 2013 11:59 AM by 984394 RSS

    strange failure in  updating status of a item in CMS.

      our weblogic portal 10.3.2 application whishes to change the status of an item in CMS (from "published" to "retired"). We know that only the owner of the item or a superadmin can change item status. The strange thing is that: we have two separate testing environment: in one it works, in the other one not (com.bea.content.AuthorizationException: User does not have update privileges on this node)
      We would like to understand why the behaviour differs in those two envs.
      Do you know which user is impersonated by a weblogic application when accessing CMS using portal API?... do you have any hints for us?
      thanks in advance