Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Unknown Hopi error (Operation not permitted) [solved]
Bowker
So I was trying to create a workflow from within a Java application by performing a statement like this:
csWorkflow = csClient.getWorkflowEngine().createWorkflow(strWF);
The error returned is below. The solution was to grant iwEveryone workflowuser to the workarea. I tried granting it to just a user group but that didn't work. I needed to use iwEveryone.
Hope this helps someone out in the future or if someone knows how to avoid giving everyone access that would be good too.
Stack trace:
toString:com.interwoven.cssdk.access.CSAuthorizationException: Unknown Hopi error(Operation not permitted)
cause:null
Stack contains 26 elements.
0 handleExceptionSci com.interwoven.cssdk.sci.exception.ExceptionHandler 188
1 handleException com.interwoven.cssdk.sci.exception.ExceptionHandler 104
2 createWorkflow com.interwoven.cssdk.sci.workflow.WorkflowServiceSciImpl 763
3 createWorkflow com.interwoven.cssdk.workflow.java.WorkflowServiceAdapterImpl 78
4 createWorkflow com.interwoven.cssdk.workflow.impl.CSWorkflowEngineImpl 225
Find more posts tagged with
Comments
Rick Poulin
In theory, you just need to grant workflowUser to the user represented by your CSClient that's creating the workflow object. Note that if you use a CSClient with System access, it typically represents SYSTEM on Windows or iwui on 'nix, so that user needs to have the workflowUser privileges as well.
In the end, the user creating the workflow needs to be allowed to own workflow jobs in the workarea where it was created.
Bowker
I totally agree with everything you said. That's were we started. I granted the access to one of the groups that the user is in after verifing the ID from the CSClient object. That didn't resolve the CSAuthenticationException. Only by adding workflowuser -> ...workarea did the issue go away.
I did not try granting the access directly to the user, but with 400 users, I didn't want to manage that. In this case, all users on the system should have the workflowuser access to that workarea so no harm.