OIF 11.1.1.4 - When trying logout of OIF as SP - 500 Internal Server Error

Question

I have one OIF instance configured as an SP and another OIF instance configured as the IdP. The IdP is integrated with OAM.
I can login successfully from the SP and I am redirected to the IdP -> OAM for Login -> IdP -> SP to target resource.
I then click a logout link - https://idmdemo.yourcompany.com:7600/fed/user/logout?returnurl=http%3A%2F%2Fsso.mycompany.com%2F
I am then redirected to IdP -> OAM (/oam/server/logout) -> IdP (https://sso.mycompany.com/fed/user/sloosso) where I get the 500 error.
Here's the exception in the log:
[2012-03-08T11:19:20.189-06:00] [wls_oif1] [ERROR] [FED-12064] [oracle.security.fed.controller.ApplicationController] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 004ifttzZ3dFw005zzw0yW00024y00054x,0:1] [APP: OIF#11.1.1.2.0] [URI: /fed/user/sloosso] Exception: {0}[[
java.lang.NullPointerException
at java.net.URLEncoder.encode(URLEncoder.java:188)
at java.net.URLEncoder.encode(URLEncoder.java:154)
at oracle.security.fed.http.flow.authn.engines.osso.OssoLogoutResponseHandler.perform(Unknown Source)
at oracle.security.fed.controller.ApplicationController.processServletRequest(Unknown Source)
at oracle.security.fed.controller.web.servlet.FederationServlet.doGet(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)

Answer 1

It appears that OAM is removing the url parameters for the p_done_url sent to it by OIF.
     302 Redirect to -> Location: https://sso.mycompany.com/oam/server/logout?p_done_url=https%3A%2F%2Fsso.mycompany.com%2Ffed%2Fuser%2Fsloosso%3Fid%3Dosso%26type%3D3&invokeOSFSLogout=false
     Result: 200. Set-Cookie OAM-ID to expired.
Form Submits: https://sso.mycompany.com/fed/user/sloosso
Result: 500 Error
Notice the p_done_url value in the redirect has extra parameters which when the Form is submitted are lost.
If I manually enter the url: https://sso.mycompany.com/fed/user/sloosso?id=osso&type=3&invokeOSFSLogout=false
Then I am successfully logged out.
This seems almost like a bug in OAM...