PeopleSoft/WebLogic proxy with Shibboleth Native SP and Apache

[Cantor, Scott]

On 1/22/13 6:19 PM, "Scott Koranda" <skoranda at gmail.com> wrote:

>I understand from the list archives that a number of campuses have
>"domesticated" or integrated PeopleSoft/WebLogic into a
>SAML2/Shibboleth infrastructure by "proxying" with the Shibboleth
>Native SP and Apache. The approach I have read the most about involves
>using the "custom sign-on API" provided by PeopleSoft/WebLogic (which
>may or may not be the same as leveraging "Signon PeopleCode"?).

That's pretty much the same, but I would note that it's really invariant.
Most of the methods of SSO-enabling it, regardless of technology, require
that step. I believe even use of Oracle's own tools might.

>I do not have any PeopleSoft/WebLogic experience but would like to
>understand if the approach using the Shibboleth Native SP and Apache
>as a "proxy" requires proxying the entire PeopleSoft/WebLogic
>application (so that no HTTP GET or POST ever go directly to
>PeopleSoft/WebLogic) or if the "proxy" is only active during the
>session initiation phase of a SSO flow.

We do it for everything, but I don't know if that's required or not. I
just note it to illustrate that it apparently isn't as insane as it might
sound.

-- Scott