The TEWS response is different on Identity Manager 12.6.x and 14.x compared to Identity Manager 12.5.x

book

Article ID: 15539

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Portal CA Risk Analytics CA Secure Cloud SaaS - Arcot A-OK (WebFort) CLOUDMINDER ADVANCED AUTHENTICATION CA Secure Cloud SaaS - Advanced Authentication CA Secure Cloud SaaS - Identity Management CA Secure Cloud SaaS - Single Sign On

Issue/Introduction

TEWS response in 12.6.x and 14.x has a TEWS keyword appended to the SOAP response. In 12.5.x the format was different. The difference between both the IDM versions are given below. 

 

Behavior on 12.5.x

<ImsException version="6.0"> 

<exception

<name/> 

<code>500</code> 

<description>DESCRIPTION</description

<transaction>TRANSACTION #</transaction

</exception

</ImsException

 

Behavior on 12.6.x and 14.x

<tews:ImsException version="6.0"> 

<tews:exception

<tews:name/> 

<tews:code>500</tews:code

<tews:description>DESCRIPTION</tews:description

<tews:transaction>TRANSACTION #</tews:transaction

</tews:exception

</tews:ImsException

 



Is it possible to revert TEWS to the legacy version where tews: is not appended into the SOAP responses? 

Environment

Release:
Component: IDMGR

Resolution

Unfortunately newer versions of the product have an upgraded version of TEWS response and there is no way to change this behavior. So, all 12.6.x and 14.x TEWS calls will have this newer response type and not identical to what was seen in 12.5.x. The software you have integrating with TEWS will have to be updated to accommodate this, there is no workaround from the Identity Manager side of this integration.