PCUI Application to be viewed externally

[Former Member]

Hi,

we have a requirement for which a PCUI application seems to be the best fit, i.e. (Search - Search Result - Detail) type of screen. However, we do not want to link this application to a Portal, instead we would like to make the application avaiable to some external Third Parties (Stateful logon). We will not be building an external portal either, it will simply be a link to a BSP wrapper which launches the PCUI BSP application. My question to all of you is, firstly, what would be the best approach ... a wrapper around the PCUI applicaiton with the appropriate logon? Considering the CRM_BSP_FRAME is a generic BSP which will hold other internally sensitive PCUI applications, what other security implications / requirements are there?

I look forward to your responses.

[Former Member · Accepted solution]

Hi Aaron

You can control the generic nature of CRM_BSP_FRAME in a couple of ways.

One is good old authorization objects. Each PCUI application has a transaction code assigned for authorization checks. You can then easily control that external users can only run certain PCUI apps regardless of URL fiddling. Then you don't need to copy CRM_BSP_FRAME.

In addition, if you create an alias in SICF for CRM_BSP_FRAME then they are not aware they are running that particular BSP. I imagine you would be using a proxy. You can filter the URLs that are allowed to be passed from the proxy to the WebAS. So, they can only run the alias.

Cheers

Dom

[Former Member]

Aaron, I think you are mentioning the biggest securit breach. Why not copy the CRM-BSP_FRAME application and add a case/if statement validating the PC-UI application and executing the BSP only when the correct PC-UI application is identified? Tiest.

[Former Member]

Hi Aaron,

remind that object links won't work outside the portal.