thanks a lot - it is great idea to do it inside Authentication activity, however, I still did not manage to make the above code to give me the input XML so far... If I try to print test - it is always equal to null.
I tried the following (did not help): test=((javax.servlet.http.HttpServletRequest)tools.getRequestor().getRequestorPage().getObject("pxHTTPServletRequest")).getParameter("requestparameters"); // returns null
and test = ((javax.servlet.http.HttpServletRequest)tools.getRequestor().getRequestorPage().getObject("pxHTTPServletRequest")).toString(); // returns com.pega.pegarules.priv.authentication.RequestFacade@8a210131
It seems to be impossible at the moment with HTTP-service, not sure about REST. The work around mentioned before - map the input to the property before parsing it - might be implemented or you may switch to using SOAP service, however, this does not solve the issue.
Hello, I´m facing the same issue. Trying to get request parameter inside Authentication Activity without success. Request object returns com.pega.pegarules.priv.authentication.RequestFacade@8a210131. Altough I´m able to get request header data. Is there any solution or workaround for that?
Thank you for posting your query on PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write a Post button that’s available on the top right pane of this page. Once created, please reply back here with the URL of the new post.
We have also sent you a private message opening up a communication channel in case you have any further questions.
We have solved this issue, but right now I do not have access to the code and cannot check exact way.
You have access to request headers within authentication activity if you use HTTP service instead of SOAP (this was the reason we used it). You should find the right way to get these parameters and as far as I understand you have found such way already.
If you want to have the access to request itself:
We did not find a way to obtain the full request with headers and body in Pega (the object is removed right after parsing before we can intervene). However, as a workaround you may change the mapping in Service HTTP rule to map to clipboard property instead of parse rules. Within the activity which is called from Service HTTP rule you may call the method apply-parse-xml to parse it after you use original request for your purposes.