OAM Logout And SSO Validation Fail With OAM-02106 From OAG Using Access Server Sdk
Last updated on AUGUST 26, 2017
Applies to:Oracle API Gateway - Version 11.1.2 and later
Information in this document applies to any platform.
OAM logout and SSO validation not working from OAG using Access Server SDK.
After integrating OAG and OAM using Oracle Access Manager Integration Guide, the user basic authentication and authorization using OAG filter is working fine.
However, when trying to use logout and sso token validation, the following exception occurs:
[ERROR] [OAM-02106] [oracle.oam.controller] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)']
[userId: ] [ecid: 0000xxxxxxxxxxxxxxxxx,0] [APP: oam_server#188.8.131.52.0] An error occurred while terminating session
The OAG log file shows the following exception in the login and the logout:
DEBUG 12/10/16, 13:51:50.185 Filter [Authorization via OAM 11gR2] completes in 116 milliseconds.
DEBUG 12/10/16, 13:51:50.185 ..."oam sso login" complete.
DEBUG 12/10/16, 13:51:50.185 add header Server
DEBUG 12/10/16, 13:51:50.185 response code: 500
DEBUG 12/10/16, 13:51:50.185 send prologue: content length -1
DEBUG 12/10/16, 13:51:50.185 peer can't do chunking
DATA HTTP/1.1 500 Internal Server Error
Date: Sat, 10 Dec 2016 06:51:49 GMT
OAM Version: 184.108.40.206.0
OAG version: 220.127.116.11.0
OAM access server sdk: 18.104.22.168.0
OS: Linux x86-64
1. Follow the steps mentioned in Oracle Access Manager Integration Guide to integrate OAM and OAG.
2. Try to logout from OAM Session.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms