Integrating Liferay into HPESC portal

1.

INTEGRATING LIFERAY INTO HPESC
PORTAL

2.

FRONT-END ARCH: CURRENT HPESC PORTAL
internal.support.hp
e.com
support.hpe.
com
Salesforce (CEP)
Pages:
IAMFacing
Portal
Apache
UIDFacing
Portal
Apache
Home Page
Search Page
Case Mgmt Pages
Header/Footer
Etc…
DWF
Proxy
SA2.0
Pages:
User Agent
(Browser)
Portal Gateway
Doc Display
SWD Detail
Service
Credits
Etc…
Feature Apps
CONFIDENTIAL | AUTHORIZED
2

3.

internal.support.hp
e.com
support.hpe.
com
FRONT-END ARCH: HPESC PORTAL + LIFERAY
IAMFacing
Portal
Apache
UIDFacing
Portal
Apache
Salesforce (CEP)
Pages:
DWF
Proxy
Home Page
Search Page
Case Mgmt Pages
Header/Footer
Etc…
Liferay
Pages:
TBD (eg
maybe Partner
Portal?)
SA2.0
Pages:
User Agent
(Browser)
Portal Gateway
Doc Display
SWD Detail
Service
Credits
Etc…
Feature Apps
CONFIDENTIAL | AUTHORIZED
3

4.

NOTES
• Liferay fronted by HPESC Portal Gateway in the same way as Salesforce and SA2.0 are
fronted (and as SA1.0 and Vignette were in the past), with all the usual gateway
services:
• Common domain
• Common login/logout orchestration including SSO/SLO
• Common locale
• URL rewriting
• GSS state (if needed)
• Etc.
• Big open question: how does Liferay need to receive user state?
• Can it be passed via GSS as with SA2.0 apps?
• Or does it need OIDC or SAML or some-such as with Salesforce?
• Or some other way?
• The answer here has big implications for complexity and performance.
– If like SA2.0 apps with GSS, minor complexity and negligible performance hit (sub-second).
– If like Salesforce with OIDC, significant complexity and performance hit (multiple whole seconds) – would
need rethink.
INTERNAL USE ONLY
4