HI + IM = Nulli

Nulli experts share their Human Information + Identity Management knowledge

WEBLIB Security - All in the Record Name

A customer recently created some custom IScript that was triggered from a page button. Pressing the button popped open a new browser window with printer-friendly text saved down from a variety of data fields on the page. Everything worked fine except that not everyone was authorized to use the button logic.  Isolating the error pointed to the custom IScript call, per the following line.

ViewContentURL(GenerateScriptContentURL(%Portal, %Node, Record.<custom recname>, Field.PRINT_BTN, "FieldFormula", "IScript_<custom IScript>"));

When implementing an IScript, the container or WEBLIB record name must be prefixed with "WEBLIB_".  So the code line above should really read something like:

ViewContentURL(GenerateScriptContentURL(%Portal, %Node, Record.WEBLIB_<remainder of custom recname>, Field.PRINT_BTN, "FieldFormula", "IScript_<custom IScript>"));

 

 

 

PeopleTools 8.51 SSO using Oracle Access Manager 11g (11.1.1.3)

For many years, Oracle has provided a well documented OAM SSO solution for PeopleSoft using typical header variable integration. However, PeopleBooks for PeopleTools 8.51 has become so, shall we say, refined, it's now harder to acheive success with such time-tested integration steps.