Highlighted
Absent Member.
Absent Member.
160 views

How to correlate UUID

Hi,
My code looks as below:
web_custom_request("NBISecurityService",
"URL=",
"Method=POST",
"TargetFrame=",
"Resource=0",
"RecContentType=text/xml",
"Referer=",
"Snapshot=t41.inf",
"Mode=HTML",
"EncType=text/xml; charset=utf-8",
"Body=
0aae75e6-ecb6-4c78-a957-18d42c923060
{userGuid}
",
LAST);

there is a correlation id in the request which is not a part of any response, in such an event how to correlate the id? also if this is nothing but the uuid then how do i embed the code for generation of UUID in the above custom request?
0 Likes
1 Reply
Highlighted
Absent Member.. Absent Member..
Absent Member..

Hi SriRupa,

Welcome to ITRC forums...!!!

UUID is strong secure token which cannot be simuated from normal correlation in VuGen. As per the global standard, UUID is based on the application defined algoritham as per the previous request in the application flow. It is close to impossible correlating this value without the help from security team & application algoritham designers. So follow the below procedure to complete this task.

1. First of all verify if the correlation ID is mandatory variable to passed in this request. If not you can simply bypass this.

2. If it is mandatory, verify with the application development team & application owner for the possibility of disabling this verification temporarily, if the end objective is to measure the performance of the application.

3. If not possible, work with application development team to reuse the UUID alogarithm to simuate the correlation ID in this request.

Hope this gives you more clarity. if you still have any issues after doing so, do let me know. Please donot forget to assign points to the ITRC responses if the answer helps you in any passion.

Thanks,
Raj


Regards,
Raj

Like this Post? Click Kudos! to show appreciation.
Is your issue addressed? Click "ACCEPT AS SOLUTION" against the post which helped you the most.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.