Hi Sowjanya,

I am not sure about your use case - what kind of parameters and why do you require them for authentication?

In a typical IAC/mashup implementation, users log in to the portal page, which then displays the applications that they have access to, including the applications displayed by the Pega gadgets. As the portal page authenticates users before allowing them access to a Pega web mashup, there is no reason to require additional identification.

Normally, you pass parameters in the following two ways - 

• using data-pega-action-param-parameters mashup attribute

Inside the div attribute in mashup code, use data-pega-action-param-parameters='{UserIdentifier:"username",Password:"password"}'

• using PegaA_params

Use PegaA_params="{UserIdentifier:'username',Password:'password'}"

Hope this helps.