UserApp and https:
When you setup the connection you specify https://server:port/IDMProv in the URL.
The Test Connection (Play button in the Connections panel) tests the connection and automatically imports the https certificate into the /keystore/truststore file.
The following scenarios provide a few examples when the error java.lang.RuntimeException is observed.:
Note that the Object Browser button and the Import Links for form fields require an eDir connection to the IDM server in order to read information from the UserApp driver object.
During work flow operation: Here the exception happens when the application is unable to read exception information from stream while executing action method approve Request.
This error is returned by the UserApp API. It is typically returned when you are specifying a piece of data for the approval form that is incorrect, or you don’t specify a piece of data that the approval form requires. It can also be returned if the workflow DN is not correct.
To get a more informative error, do the following:
Login to UserApp as the user app admin.
Administration -> Logging -> Change log level of all above logs (set to Debug).
Submit.
Then run your test again and look in the User App log file:
IdentityManager/rbpm/jboss/server/IDMProv/log/server.log
Look for something like:
APPROVE failed com.novell.soa.af.impl.soap.AdminException={_Reason=Data item [reason] is not defined for activity or provisioning request}
In this case, an attribute of “reason” was included in the Approve Request action in Identity Validator, but “reason” was not on the approval form.
Bad content: Here the exception happens when you try to start a work flow. This can be because of an invalid URL used in the UserApp server.
You will see the following error message:
Error while executing action method startWorkflow: java.lang.AssertionError: java.lang.RuntimeException: java.io.IOException: bad content type = text/html; charset=iso-8859-1; Received Content:
Invalid entry: Here a runtime exception happens, when for a field in the approval form you specify that field name as an "attribute" in the Approve Request action.
You may have a field in the approval form, but if you specify that field name as an “attribute” in the Approve Request action in Identity Validator 2.0, you receive the RuntimeException.
Specify a default value for the field in the approval activity in the workflow as follows:
In Designer, click the approval activity in the workflow.
Click Data Item Mapping tab -> Pre Activity.
Specify two single quotes (apostrophes) for the Source Expression of the Target Form Field that is causing the error. This gives the field an initial empty value which allows the User App api to recognize the field.
Start and approve workflow: Starting a workflow and immediately trying to approve it may result in an error:
No task for this process/user while executing action method approveRequest.
The approval tasks allow you to specify a retry count which will allow you to retry until the task becomes available.
If you try another action that does not have a retry counter, use a wait action to delay for a few seconds.
This connector allows you to grant, revoke, and assert Roles and Resources. You can also do this manually using the eDirectory connector (Path syntax actions) if the actions in this connector is not sufficient.