Well, people might find it a bit stupid about the Post Title, but there are some surprises. In our production environment, we have Oracle Portal 22.214.171.124.0 and OAM 10.1.4.3. As usual, using the traditional approach we have used OSSO 10g to integrate Oracle Portal with OAM 10.1.4.3.
The surprise here is that: Oracle Portal 126.96.36.199.0 has never certified Oracle Portal 188.8.131.52.0 with OAM 10.1.4.3. However OAM 10.1.4.3 is certified with OSSO 10g (we used 10.1.4.3) and Oracle Portal 184.108.40.206.0 is certified with OSSO 10g (10.1.4.3). However SSO 10.1.4.3 delegating authentication to OAM with Oracle Portal is an unsupported configuration. Well, this is true for Oracle Portal 10g and OAM 10.1.4.3 too .
The OAM 10.1.4.3 FAQ document talks about that. Points 4 and 5 talks about that.
Just to notify the Oracle Consultants out there that if you have a Oracle Portal and OAM in your architecture, it is good to validate with Oracle during project bidding time otherwise you may not receive support from Oracle for an unsupported configuration.
Coming to the supported version: Oracle Portal 220.127.116.11.0 and Oracle Access Manager 18.104.22.168.x+
You must upgrade OAM to 11g and Portal to 22.214.171.124.0.
I am engulfed in Oracle Identity & Access Management domain. I have expertise on providing the optimized solutions for user provisioning, web access management, Single Sign-On and federation capabilities etc., I am also well versed with complex integrations within Identity Management and other product domains. I have expertise on building demos and implementation experience on products Oracle Access Manager, Oracle Adaptive Access Manager, Oracle Entitlement Server, Oracle Virtual Directory, Oracle Internet Directory etc., Look @ my blog: http://talkidentity.blogspot.com