Clarity

Hi All,

We are facing a strange issue with process execution. The process is failing with custom script XOG username and password as Invalid.

But we have set the correct user name and password which is available for the same user in system.

While setting again the process custom script user and password, the password gets changed to some other value. Not sure why it is not allowing to change the password and change it to a default value.

Any way to check what password it is setting for custom script? We are trying to change the password by keeping the process in draft mode.

Thanks,

Pragya Singh

Why would you want to store the password and use because if you refresh environment you are going to have the same and all old instances still going to use the old value where process was in execution stage. The best would be to use the PPM session to authenticate and execute. 

Hi Pragya,

Couple of things to check:

1) Try to carry out a simple XOG directly, using the preferred username and password and check if that succeeds 

2) If you are running the a XOG through a script in the process, then check the script. Ideally, the script could pick up username from session / properties.xml , however check if any username is hard coded in the script, or check the reference of the username in the script.

For example in the script, check if there is any kind of set users:

<!--parameter section-->
<gel:parameter default="sample_db_username" var="p_DBname"/>
<gel:parameter default="sample_xog_username" var="XOG_USER"/>

Check how the password is getting referenced in, ideally it should be through sessions , for example:

<!--Log into clarity by initialising class instance-->
<core:set value="${userSessionCtrl.init(XOG_USER, v_secId)}" var="v_secId"/>
<core:set value="${v_secId.getSessionId()}" var="xogSessionId"/>
<core:if test="${DEBUG==2}">
<gel:log category="GEL" level="INFO">Session ID: ${xogSessionId}</gel:log>
<gel:log category="GEL" level="INFO">Username: ${v_secId.getUserName()}</gel:log>
<gel:log category="GEL" level="INFO">User Status: ${v_secId.getUserStatus()}</gel:log>
<gel:log category="GEL" level="INFO">Is User Logged In: ${v_secId.isUserLoggedIn()}</gel:log>

You can use gel logs for further reference, however passwords are usually encrypted.

Third, when you save the process on CA PPM, check the Gel parameters if anything has been inputted there in the GUI

Hope this helps.

Regards,

Samik

Hi,

Whatever username and password we are giving in the custom script, it is showing could not login message.

The same user is working fine for other process custom scripts.

Thanks,
Pragya

Hi Pragya,

How are you referencing the user in the script , i.e. the manner in which you are referencing / fetching / setting the password for this user in the script ?

Also in the gel parameters do you see the same user being referenced:

Example:

You may want to open a support ticket for detailed review.

Regards,

Samik

Hi

samik has already provided to get user session ID by passing username. not password. 

For best practice,

Don't pass user name and password in the gel script to get XOG session ID.  if you using this solution, better to change the solution to get XOG session ID by passing XOG user name only. this will help to avoid Process failure whenever password getting changed.

Thanks

Senthil

Hi All,

The issue is fixed now.

We were not passing the username and passwords in the gel script, it was supplied through custom parameter tab.

We re-created the process and first ran the process only with the gel script to connect and get the session id for XOG.

Then modified the process to add further processing steps. This worked for us.

Not sure why same credentials did not worked for older process.

Thanks,

Pragya Singh