Question

IAC Login

I am following the course Customizing the User Experience which has exercise for Creating Pega Web Mashup.

I have followed exercise steps and generated mashup code. It looks like below:

<script src ='http://192.168.1.10:9080/prweb/PRServlet?pyActivity=pzIncludeMashupScripts'></script>
<div data-pega-gadgetname ='PegaGadget'
data-pega-action-param-parameters ='createNewWork'
data-pega-action-param-classname ='ABB-ReserveIt-Work-Listing'
data-pega-action-param-flowname ='pyStartCase'
data-pega-action-param-model =''
data-pega-isdeferloaded ='false'
data-pega-applicationname ='ReserveIt'
data-pega-threadname ='STANDARD'
data-pega-systemid ='pega'
data-pega-resizetype ='stretch'
data-pega-url ='http://192.168.1.10:9080/prweb/PRServlet'
data-pega-redirectguests ='false'
>
</div>

I have added above code to test webpage provided with exercise. But when I access the webpage with url http://192.168.1.10:9080/Listing.html. it just shows me Pega login screen. How do I get past login screen (Do I need to send username and password through gadget somehow?) and mashup create the work object?

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Correct Answer
August 27, 2018 - 10:21pm

Hello Sachin, 

You need to provide authentication credentials to IAC Page so that it will render appropriate Harness or Section you are referencing in Mashup code. Please find the reference document I have attached. 

Comments

Keep up to date on this post and subscribe to comments

August 27, 2018 - 10:21pm

Hello Sachin, 

You need to provide authentication credentials to IAC Page so that it will render appropriate Harness or Section you are referencing in Mashup code. Please find the reference document I have attached. 

October 31, 2018 - 1:09pm
Response to Naveen_Naanu

Hi Sachin,

As per the IACAuthentication activity this expects the user id in header in production. We have implemented mashup to onboard one Pega instance inside another Pega instance. We are now struggling how to pass the user id in http header from the host pega instance to remote one. Can you please let me know if you have any idea in this?

Thanks,

Deep

December 3, 2018 - 1:48am
Response to Naveen_Naanu

I am using the below code to display harness but still it's showing the login screen.

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><br/>
<htmllang="en"><br/>
<head><br/>
<metahttp-equiv="content-type"content="text/html; charset=utf-8"><br/>
<title>Pega Web Mashup Page</title><br/>
</head><br/>
<body><br/>
<p>This page will host a Pega Web Mashup</p><br/>
<!-- ********************** Begin Pega content ********************** --><br/>
<script src ='http://localhost:8080/prweb/PRServlet?pyActivity=pzIncludeMashupScripts'></script>
<div
style="overflow:auto height:600px"
data-pega-gadgetname ='PegaGadget'
data-pega-action ='display'
data-pega-action-param-classname ='Data-Portal'
data-pega-action-param-harnessName ='pyCaseManager7'
data-pega-isdeferloaded ='false'
data-pega-applicationname ='DMSample'
data-pega-threadname ='STANDARD'
data-pega-resizetype ='stretch'
data-pega-systemid='pega'
data-pega-action-param-parameters ={UserIdentifier:test,Password:'cnVsZXNAMTIz'}
data-pega-redirectguests ='false'
data-pega-url ='http://localhost:8080/prweb/PRServlet' ></div>
<!-- ********************** End Pega content ********************** --><br/>
</body><br/>
</html>           

 

August 27, 2018 - 10:42pm

Cool. That worked. Thanks Naveen.

What I was missing was base-64 encoded password. I was passing it as plain text.

By the way, in real-world implementation,what is way to achieve this? Do we still pass userid and password  parameters like this or will it be through third party authentication (SSO) etc?

 

 

 

 

August 27, 2018 - 11:05pm
Response to SachinN6

Thanks for the update Sachin. 

While Generating Mashup code, We believe the source URL will be "IAC" preceded by your hostname which uses basic authentication of your operator. In case if URL includes "SSO" system may request for SSO login, that will no longer render the Harness content you are referring in Mashup code (Haven't tested - Not recommended by Pega).