Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

3
Replies
771
Views
 Gowri Deivaraju (GowriD25) WellsFargo Lead Software Engineer
WellsFargo
US
GowriD25 Member since 2015 10 posts
WellsFargo
Posted: Jul 6, 2017
Last activity: Jul 11, 2017
Posted: 6 Jul 2017 17:11 EDT
Last activity: 11 Jul 2017 23:44 EDT
Closed

Public access application

Report

Hello there,

I have a requirement to build a PEGA application exposed to public, no login is required to access the application.

I see a lot of related posts but no concrete answers. What is the best approach to implement this? please suggest

Thanks

Gowri

Low-Code App Development Security
Posted: 5 years ago
Posted: 6 Jul 2017 23:28 EDT
Bala Gangadhar Tilak Cherukuri (cherb) PEGA Manager, Technical Support - User and Product Experience
Pegasystems Inc.
IN
Report

Hi Gowri,

I can say that we can achieve the requirement two ways.

Approach 1:-

In PRPC, all the rules that does not require login should go under unauthenticated ruleset. You can have a look at PRPC:Unauthenticated OOTB ruleset once. You can also create your own unauthenticated ruleset and save all the rules those need to be exposed to public and configure your Requester Type rules of Type Browser with new unauthenticated ruleset

Approach 2:

By using Pega Mashup (Pega Internet Application Composer). Configure Pega IAC in the environment and expose your portal harness using Gadget Manager with administrator credentials. You will get a html with div after successful completion. You can expose this html to public. However, there as some limitation with Pega IAC where prior Pega 7.2 application must obey the same origin policy.

Please feel free to reply for any thoughts

Thank you,
Posted: 5 years ago
Posted: 7 Jul 2017 16:49 EDT
Gowri Deivaraju (GowriD25) WellsFargo Lead Software Engineer
WellsFargo
US
Report

Hi Cherb,

   Thanks for you response. I have one concern with Approach 1, we want to expose certain search features in a internal application to public. And this application is built on top of enterprise ruleset. All these rulesets cannot be exposed to unauthenticated access group right?.

Can we use a dummy use profile login for all the public users? Do you see any issues with this approach?

There would be multiple session with the same id, I hope this should not be an issue.

Thanks

Gowri 

 
Posted: 5 years ago
Posted: 11 Jul 2017 23:44 EDT
Bala Gangadhar Tilak Cherukuri (cherb) PEGA Manager, Technical Support - User and Product Experience
Pegasystems Inc.
IN
Report

Hi Gowri,

I dont think that there is a restriction on ruleset exposed to unauthenticated access group as we are trying to add the enterprise ruleset to production ruleset list of unauthenticated access group.

you can use a dummy profile login, However I prefer to use password in Base64 encode format. PRPC accepts unliminted concurrent session for the same user. The property which handles this is pyConcurrentSessions. This should not be an issue.

Please feel free to add your comments or thoughts if any.

Thank you,

 

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

Pega Collaboration Center 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