This content has been marked as final. Show 5 replies
It’s a great document. We have fixed the routing issue by changing the node password correctly. But getting the another error like
+"User %1 is not authorized to invoke service operation %2"+
When I have checked the roles and permission lists , the user has the proper roles. That roles-permission list is tagged to the service operation in both the DB.
Below sql gives result for my SO.
select * from sysadm.psroleuser where roleuser=<user id > and rolename in (
select rolename from sysadm.psroleclass where classid in (
select classid from sysadm.psauthws where IB_OPERATIONNAME in (<SO NAME>)));
not sure how this error is occuring?
You should check which permission list the service operation is attached to, and check if the user has been granted to, Something like the following from the backend :
If nothing is returned for your user, then you could created a new role and give it to the user.
SELECT distinct c.roleuser FROM psclassdefn a, psroleclass b, psroleuser c WHERE a.classid = b.classid AND b.rolename = c.rolename AND a.classid = '<permission_list>'
Also, since you are on Peopletools 8.52, all this configuration settings can be done through Integration Network WorkCenter. I wrote articles about that (and you can find something about permission list for a given service operation as well) :