To this end, an External Application GXportlet is needed. In this GXportlet, configure the following properties: Origin to indicate the application URL and Add security parameter.
In addition, the application must have these settings:
-
It must receive a variable of Character (254) type in a parameter. This variable will allow you to obtain the details of the user logged in to the site. (*)
-
It must make a SOAP invocation to the external web service pgxpws001 that is distributed with GXportal's frontend programs. This web service validates the user and returns the session status and user’s details.
Example:
(*) This parameter received by the external applications is made up of the following data:
Code of the Language in which the portal is visualized (“S” = Spanish, “E” = English, “P” = Portuguese, etc.)
Portal code
Channel code
Page code
Sector code
GXportal User code
Status in which the portal is being visualized (in production = “O” or in design = “P”)
Encrypted key
The first 7 values of this parameter (delimited by “;”) can be directly used by the external application (they are not encrypted). When the user session verification service is executed (web service), GXportal confirms if the user can access the page and the channel received as parameter.
When executing the GXportal web service, a return code higher than zero will be obtained to indicate the error type. If the session is valid, the return code is zero and the user data detailed below is also returned.
Error code :
0 Valid user session
1 Anonymous user
2 Invalid page
3 Missing encrypted key
4 Invalid encrypted key, it does not correspond to the session
5 Encrypted user does not match user code
6 Invalid session
User code (in GXportal)
External user code (in the external base)
Login name
GXportal Profile ID
External Profile ID
Last name
Name
Portal code
Channel code
Page code
Page sector code
Status in which the portal is being viewed
The first thing that each external application program must do is calling the GXportal web service to validate the user session. To avoid excessive calls to the service, the external application can make it once and then save a cookie to identify the user, or use another session method for the application internal users. If a cookie is saved, it should be deleted when the browser is closed.
The first 7 values of this parameter (delimited by “;”) can be directly used by the external application (they are not encrypted). When the user session verification service is executed (web service), GXportal confirms if the user can access the page and the channel received as parameter.
The first 7 values of this parameter (delimited by “;”) can be directly used by the external application (they are not encrypted). When the user session verification service is executed (web service), GXportal confirms if the user can access the page and the channel received as parameter. The first 7 values of this parameter (delimited by “;”) can be directly used by the external application (they are not encrypted). When the user session verification service is executed (web service), GXportal confirms if the user can access the page and the channel received as parameter.The first 7 values of this parameter (delimited by “;”) can be directly used by the external application (they are not encrypted). When the user session verification service is executed (web service), GXportal confirms if the user can access the page and the channel received as parameter. Portal codePortal code Portal code Portal codePortal code