My Oracle Support Banner

Integrating Oracle BI Enterprise Edition with PeopleSoft - without an SSO product (Doc ID 1074402.1)

Last updated on NOVEMBER 27, 2019

Applies to:

Business Intelligence Suite Enterprise Edition - Version [1900] and later
Information in this document applies to any platform.


This document is aimed at implementors familiar with both PeopleSoft and Oracle Business Intelligence Enterprise Edition technologies.  In particular, implementors should have experience of building and maintaining objects in PeopleSoft Application Designer as well as building and maintaining metadata in the Oracle BI Administration Tool.  Access to the relevant functionality in both of these tools is a prerequisite for completing the integration described in this document.


Customers should be aware that there are some limitations of this alternative approach.  The known limitations are as follows:


  1. Once authenticated into both PeopleSoft and Oracle BI EE, a user session on PeopleSoft may timeout whilst the user session on Oracle BI EE remains valid.
  2. A user session on Oracle BI EE may timeout whilst the PeopleSoft session remains valid.
  3. Signing out from PeopleSoft will not automatically sign the user out of Oracle BI EE.
  4. Signing out from Oracle BI EE will not automatically sign the user out of PeopleSoft
  5. When signing out from Oracle BI EE, the token generated by PeopleSoft will still be valid for re-authenticating the user in Oracle BI EE until it expires.
  6. PeopleSoft Users will only be able to access Oracle BI EE via embedded links in the PeopleSoft Application (i.e. it is not possible to login to Oracle BI EE directly using PeopleSoft UserID and Password).
  7. Users defined directly in the Oracle BI EE RPD can co-exist with users defined in PeopleSoft, but these users will not be able to link back to PeopleSoft without being challenged to login to PeopleSoft.
  8. This method involves passing a UserID and a Token via http from PeopleSoft to Oracle BI Enterprise Edition.  For security reasons, it is recommended to use SSL and the http post method.
  9. The method and code described in this document may need to be localized by the customer.  For example, when converting http dates to a database format.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.