This content has been marked as final. Show 8 replies
knowledge note# 562807.1 (Configuring an APEX Application to Use SSO With SDK in Separate Schema [ID 562807.1]) at http://support.oracle.com/ will provide you all the details you need to set this up on your internal system. BTW, there are also several other knowledge notes regarding SSO, just restrict the knowledge base search to "Application Express" and search term "sso".
My Blog: http://www.inside-oracle-apex.com
APEX Plug-Ins: http://apex.oracle.com/plugins
Thank you for your reply. Was able to complete step A. INSTALLING THE SSO SDK INTO A NEW SCHEMA using knowledge note - 562807.1. All sequences, tables, procedures, and packages were created with no errors. Ran subsequent 3 Grants:
grant execute on wwsec_sso_enabler_private to APEX_040100; <Grant succeeded>
grant select on wwsec_enabler_config_info$ to APEX_040100; <Grant succeeded>
grant execute on wwsec_sso_enabler_private to LEARNER; <Grant succeeded> LEARNER is the applications parsing schema.
When I move onto to step B. REGISTER APEX AS PARTNER APP IN SSO, and follow steps to visit 1. Go to the SSO Administration home and login:
http://machine.domain:port/pls/orasso/orasso.home, in my case http://127.0.0.1:9080/apex/orasso/orasso.home, I receive the
404 Not Found - The requested URL /apex/orasso/orasso.home was not found on this server.
The default Apex url I'm running locally is http://127.0.0.1:9080/apex/f?p=.... I reviewed several Apex knowledgebase articles but had no luck finding a solution..
Thanks again in advance for any guidance for moving beyond this point... -Mike
Your URL appears incorrect.
The URL http://machine.domain:port/pls/orasso/orasso.home is where the Oracle Login Server is installed and running. This isn't an APEX application. Your URL should not be http://127.0.0.1:9080/apex/orasso/orasso.home. You should use the URL where you have successfully logged into the administration of Login Server.
I hope this helps.
Thank you Joel for your reply. And real sorry for the newbie follwup questions.
Since I am running Apex and Oracle 11g instances & schemas locally would the administration of Login Server (and registering my Apex project as a partner application) be done locally, e.g. http://127.0.0.1:port/pls/orasso/orasso.home. Or is the administration of Login Server something I need to get Oracle IT involved in through an APS request? Many thanks again!
If you're running your own Login Server, then the administration responsibility is yours. If you wish to hook up to your corporate SSO server, then you'll need to register it with them.
I hope this helps.
Thanks for your reply Joel.
I have just 1 more related newbie followup question. What is the process with registering our Apex server with the corporate SSO server? Do I open an iSupport ticket or APS request and include the Home, Login, Logout urls? Are these steps already available somewhere?
Many thanks again!
I think I'm making progress but have a clarifiucation on which directory to install the SSO SDK. It seems from KM doc ID 562807.1 the SSO SDK should be installed into a new schema called APEX_SSO. But the How-To Document Configure an Application Express Application as a Partner Application in Oracle AS Single Sign-On (link > http://www.oracle.com/technetwork/testcontent/sso-partner-app-100552.html#INSTALL) refers to installing the SDK into the FLOWS_xxxxxx schema ("Note: The
ssosdk_schema_name and SSOSDK schema mentioned in the Readme.txt refer to the FLOWS_xxxxxx."). So which is the correct schema to install the SSO SDK, a) "APEX_SSO" or b) "FLOWS_xxxxxx"?
And my next question is which schema should I run the example partner application from, again a) or b) as mentioned above?
And please let me know if I need to remove the SSO SDK from the "APEX_SSO" since that's what I used initially as the schema based on steps in KM 562807.1.
I always put the SSO SDK into a separate schema named APEX_SSO. If you put the SSO SDK into the APEX schema, then you'll have to reload the SSO SDK and re-register your application every time you perform an APEX upgrade. If you put it into a separate schema, then on an APEX version upgrade, you simply need to issue a few grants and adjust some synonyms and you're done.
As far as where to go to request this from within Oracle, send me an email and I'll send you the link. I'm prohibited from referencing an internal URL in this public forum.