This content has been marked as final. Show 4 replies
I have configured it for working with Weblogic in the role of a Service Provider (SAML2). Steps:
1. Configuring a Service Provider Site for SAML 2.0 Single Sign-On (http://docs.oracle.com/cd/E24329_01/web.1211/e24422/saml.htm#i1109029)
2. Deploy a Web application for using the HttpProxyServlet. Aim: proxy user request to OHS (http://docs.oracle.com/cd/E24329_01/web.1211/e21049/progservlet.htm#WBAPP284)
3. Configure OHS dads.conf. Basically set your PlsqlCGIEnvironmentList (http://docs.oracle.com/cd/E14571_01/portal.1111/e12041/concept.htm)
4. Configure HTTP Header Variable Authentication scheme in APEX (http://docs.oracle.com/cd/E23903_01/doc/doc.41/e21674/sec_authentication.htm#CIHEBJEH). The header name MUST be the same as in your PlsqlCGIEnvironmentList
Hope it helps,
I believe you also responded and contributed at a Java Oracle SOA blog on this topic, so I am wondering if this posting is basically the same steps we should be using that you were describing there. Or is the posting here more oriented toward a mod pl/sql configuration of Apex -- step 3 in particular?
Any clarification would be appreciated.
Sorry for the late reply. Yes basically are the same steps...
Yes, your approach worked well for us with CAS authentication using Weblogic as our app server.