I would check the console - not ISC (I assume you mean ISC not SSUI when referencing ISIM Selfservice Portal - but this is not clear).
The problem is ACIs - to find what ACI is missing you can raise the level of authorization in EnroleLogging.properties to DEBUG - be aware that it produces a lot of output and you will need some time to go through the output...
In general there are subtle but important differences between the console, SSUI and ISC when it comes to processing requests.
The console is most like the API - so it is the "reference" platform to use - if it works there it will mostly work all the other places although I know some special cases in earlier fixpaks where there are subtle differences.
ISC works using Access Entitlements - they are not governed by ACIs but provisioning policies - so if a user is not entitled to an Access Entitlement ýour request will fail. Be aware although that Access enabled Roles follow the ACI logic.
When doing something in context of an ISIM administrator all ACIs are disregarded (but not policies).
HTH to find the problem...
------------------------------
Franz Wolfhagen
------------------------------
Original Message:
Sent: Sat October 05, 2019 10:59 AM
From: Jahanzaib Sarwar
Subject: ISIM Request Account through Web Services
Hello all,
We are using ISIM Web Services to create/modify accounts on a particular service using ITIM Admin's session. The flow is working fine and ITIM Admin is able to create/modify accounts successfully on behalf of users.
Now what we need to do is, allow a user to modify account for himself/herself through our portal from where we are calling ISIM Web Services (just like request account is executed by user using ISIM Self Service portal).
As part of our testing, when we create Web Services session using ITIM Administrator, the account is modified successfully for a user whereas if we create the session using the user's credentials, we receive the error:
com.ibm.itim.ws.services.WSApplicationException: CTGIMS009E You do not have the authority to perform this operation.
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(Unknown Source)
at com.sun.xml.internal.ws.client.sei.StubHandler.readResponse(Unknown Source)
at com.sun.xml.internal.ws.db.DatabindingImpl.deserializeResponse(Unknown Source)
at com.sun.xml.internal.ws.db.DatabindingImpl.deserializeResponse(Unknown Source)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown Source)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown Source)
at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(Unknown Source)
at com.sun.proxy.$Proxy36.modifyAccount(Unknown Source)
at com.highrise.isim.ws.ManageAccount.modifyIsamAccount(ManageAccount.java:307)
at com.highrise.isim.ws.MyClient2.main(MyClient2.java:125)
What could be the possible reason as the same user is able to request account using ISIM's default Self Service Console?
Regards,
------------------------------
Jahanzaib Sarwar
------------------------------