No GUID value when getting PRD definitions through REST.

Hi,

Im currently working on calling the REST services in order to start a PRDs as an authenticated user. But I'm not getting the expected response.

I would expect when calling the getDefinitions that every PRD should have a GUID, so that it's possible to start the workflow.
But here is what I get (It's the same for uaadmin by the way):

[
{
"Links": [
{
"Link": "\/RIS\/wf\/processes?filter=Definition=cn=cjg_test,cn=RequestDefs,cn=AppConfig,cn=ua01,cn=IDMDriverSet01,ou=system,o=top",
"Type": "wf\/processes",
"Value": "Workflow Processes"
},
{
"Link": "\/RIS\/wf\/workitems?filter=Definition=cn=cjg_test,cn=RequestDefs,cn=AppConfig,cn=ua01,cn=IDMDriverSet01,ou=system,o=top",
"Type": "wf\/workitems",
"Value": "Workflow Workitems"
}
],
"DataItems": [],
"DN": "cn=cjg_test,cn=RequestDefs,cn=AppConfig,cn=ua01,cn=IDMDriverSet01,ou=system,o=top",
"GUID": "",
"Link": "\/RIS\/wf\/definitions",
"Value": "cjg_test",
"Category": "accounts",
"DigitalSignatureType": "not-required",
"Description": "cjg_test",
"Operation": "0",
"Recipient": ""
}
]

As you can se there is no GUID value nor any Link for starting the process. It's the same for all PRDs.

Heres what Iv'e done so far:
- Changed the USER_APP_URL in the web.xml in the RIS.war, pointing it to the correct URL.
- Changed the "WorkflowService/SOAP-End-Points-Accessible-By-ProvisioningAdminOnly" setting in the ism-configuration.properties to false

The system is running on Windows Server 2012 R2
IDM (DirXML) version: 4.5.3.0 AE
UA version: NetIQ Identity Manager Home Page version 4.5.3
eDir version : eDirectory for NT x86_64 v8.8 SP8 [DS]

Best regards
Carsten Jørgensen
  • On 9/5/2017 11:04 AM, cajitq wrote:
    >
    > Hi,
    >
    > Im currently working on calling the REST services in order to start a
    > PRDs as an authenticated user. But I'm not getting the expected
    > response.
    >
    > I would expect when calling the getDefinitions that every PRD should
    > have a GUID, so that it's possible to start the workflow.
    > But here is what I get (It's the same for uaadmin by the way):
    >
    > [
    > {
    > "Links": [
    > {
    > "Link":
    > "\/RIS\/wf\/processes?filter=Definition=cn=cjg_test,cn=RequestDefs,cn=AppConfig,cn=ua01,cn=IDMDriverSet01,ou=system,o=top",
    > "Type": "wf\/processes",
    > "Value": "Workflow Processes"
    > },
    > {
    > "Link":
    > "\/RIS\/wf\/workitems?filter=Definition=cn=cjg_test,cn=RequestDefs,cn=AppConfig,cn=ua01,cn=IDMDriverSet01,ou=system,o=top",
    > "Type": "wf\/workitems",
    > "Value": "Workflow Workitems"
    > }
    > ],
    > "DataItems": [],
    > "DN":
    > "cn=cjg_test,cn=RequestDefs,cn=AppConfig,cn=ua01,cn=IDMDriverSet01,ou=system,o=top",
    > "GUID": "",
    > "Link": "\/RIS\/wf\/definitions",
    > "Value": "cjg_test",
    > "Category": "accounts",
    > "DigitalSignatureType": "not-required",
    > "Description": "cjg_test",
    > "Operation": "0",
    > "Recipient": ""
    > }
    > ]
    >
    > As you can se there is no GUID value nor any Link for starting the
    > process. It's the same for all PRDs.
    >
    > Heres what Iv'e done so far:
    > - Changed the USER_APP_URL in the web.xml in the RIS.war, pointing it to
    > the correct URL.
    > - Changed the
    > "WorkflowService/SOAP-End-Points-Accessible-By-ProvisioningAdminOnly"
    > setting in the ism-configuration.properties to false
    >
    > The system is running on Windows Server 2012 R2
    > IDM (DirXML) version: 4.5.3.0 AE
    > UA version: NetIQ Identity Manager Home Page version 4.5.3
    > eDir version : eDirectory for NT x86_64 v8.8 SP8 [DS]


    Does the REST start workflow call require the GUID of the PRD? I would
    have assumed it used the DN. (I have not actually tried the REST
    services). Additionally my understanding is that the REST APIs are in
    the process of moving. Were in RIS.JAR and moving to... Somewhere...


  • Hi Geoffrey.

    Thank you for your reply.

    Yes it is necessary to have the GUID for starting a PRDs through REST. The documentation states the following:

    ----------------------------------------------------
    /v1/wf/definitions/{definition ID}
    Returns a specific workflow definition (JSON Object) available in the Workflow system.

    The following HTTP methods are supported with this URI:

    GET - Returns a specific workflow definition (JSON Object) with all the details. This will include the data items associated with that definition.

    PUT – Not supported.

    POST – Start a work flow process.

    DELETE – Not supported
    ---------------------------------------------------

    Iv'e tried it a while ago in another environment (running on linux) without any issues.

    The problem still persists, so any idea is appreciated.

    Regards
  • Did you find a solution for this problem? It seems, this is a general issue.

    Wolfgang

    On 06/09/2017 09:04, cajitq wrote:
    >
    > Hi Geoffrey.
    >
    > Thank you for your reply.
    >
    > Yes it is necessary to have the GUID for starting a PRDs through REST.
    > The documentation states the following:
    >
    > ----------------------------------------------------
    > /v1/wf/definitions/{definition ID}
    > -Returns a specific workflow definition (JSON Object) available in the
    > Workflow system.-
    >
    > The following HTTP methods are supported with this URI:
    >
    > GET - Returns a specific workflow definition (JSON Object) with all the
    > details. This will include the data items associated with that
    > definition.
    >
    > PUT � Not supported.
    >
    > POST � START A WORK FLOW PROCESS.
    >
    > DELETE � Not supported
    > ---------------------------------------------------
    >
    > Iv'e tried it a while ago in another environment (running on linux)
    > without any issues.
    >
    > The problem still persists, so any idea is appreciated.
    >
    > Regards
    >
    >

  • Hi Wolfgang.

    No I did not find a solution.
    Ended up using the SOAP endpoint insted because it also offered starting PRDs and I was told that the current REST endpoint is being depricated from 4.7 and forward.

    Kind Regards
    Carsten Jørgensen
  • Yeah, the old REST calls had some serious deficiencies.
    Need to play with the new IDM 4.7 REST calls to see how they do.

    Thx
    Wolfgang

    On 20/06/2018 09:54, cajitq wrote:
    >
    > Hi Wolfgang.
    >
    > No I did not find a solution.
    > Ended up using the SOAP endpoint insted because it also offered starting
    > PRDs and I was told that the current REST endpoint is being depricated
    > from 4.7 and forward.
    >
    > Kind Regards
    > Carsten J�rgensen
    >
    >