Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

PRSecurityException: Unknown Application error on Mashup login

SA-55075

Summary



An application is accessed through a mashup. The page hosting the mashup is generated in an Angular 5 application. The Angular application performs lazy loading. PRSecurityException occurs when accessing the URL.


Error Messages



Error message in the log:

Unknown Application <AppName> (or) verify the environment variable "/Authentication/RedirectGuests" is set to false if you are using gateway.


Steps to Reproduce

  1. Access the required application through a mashup
  2. Generate the page hosting the masuhp, in an Angular 5 application. The Angular application performs lazy loading.
  3. In Angular, load the DIV, for use by the Pega application, and the mashup scripts.
  4. Initiate the addGadget and doAction load are called as below after loading the above.

    // console.log((<any>window).pega.web.api);
    (<any>window).pega.web.api.addGadget("pegaMashUp", window);
    (<any>window).pega.web.api.doAction(this.dataPegaGadgetName, "load");

     
  5. In the mashup arguments, set the defer load to true. At this point, the browser requests the passivation activity.

    http://hostname:port/prweb/PRServletCustom/!CustomUI/$undefined?pyactivitypzZZZ=fff291ed0a657705ecee825c3a292d712d318b9ed3da5bfe82f8a4bbb4ca773a4f61d18e9de65526d3fe42ae1732c0dbc35ef9fce0e5aff27ce07c64291d36ca0cd483978320e9fd159caf14fb8ca6c8c6e50c95b58565f1f659a11e17e98383c7f184bb57e0e6d84db58e9d04df304b16e270fc017ff14629da55c984739dcc*

Root Cause



The mashup requestor has a dependency on the Browser type requestor rule. The default access group selected in this requestor rule attempted to validate the application name passed from the mashup code.
Exception occurred when the application referred by the default access group did not match with the application name referred in the data-pega-applicationname mashup parameter.


Resolution



Perform the following local-change:
  1. Update the Browser requestor type
  2. Select an access group that points to the required application.

Published October 11, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us