3 Replies Latest reply: Mar 20, 2013 9:38 AM by 991448 RSS

    Integration of External application with SSO


      We have few housemade applicaitons which as per oracle are external applicaiton.
      We want to use SSO for those applicaiton also alongwith EBS R12.
      Also we have multiple domains as below e.g. As we acquired another company so we want few finance users from new company to login to our EBS.
      domain 1 : users in abc.com
      domain 2 : new users in xyz.com

      Could you please let me know how can we acheive this . . .


      Edited by: user1115248 on Mar 14, 2013 11:26 PM
        • 1. Re: Integration of External application with SSO
          Any updates please . . .
          • 2. Re: Integration of External application with SSO
            This link has some answers to your questions and will help you to get some basic understanding of OAM 11g cross-domain capabilities - http://docs.oracle.com/cd/E14571_01/doc.1111/e15478/sso.htm .Also you might want to look into OIF for standards based multiple/cross domain sso, if you are interested.

            For your custom applications, you need code changes to read unique identifier (e.g. UID) from http headers (inserted by OAM during authentication). You can build logic around your custom application login module to consume the header and perform SSO. OAM also provides api to build custom agents if your application server is not supported for webgates. There are quite a few options here and you can take a long term and holistic view of your enterprise and arrive at a design solution.

            • 3. Re: Integration of External application with SSO
              We are also trying to achive the same thing. We are using ASDK 11g agent for applications which cannot be proetcted by webgates. Also we are using custom plugins for generating the required custom cookeis. For trusting custom cookies we are using OAM security token service. The work is still in progress and we have opened a couple of SRs with oracle. But the major issue for us that we are in OAM 11.1.1 which are very limited asdk apis as compared to