search cancel

The TEWS are drastically different between 12.6.x and 14.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 calls between 12.6.x and 14.x changed drastically. In 12.5.x the format was very different. Below is only one of many examples.

Other examples include filter and subject changes.

 

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

Occasionally newer versions of the product will include changes to our TEWS interface. There is no way to change this behavior. So, all 12.6.x TEWS calls would need to be updated in the software you have integrated with TEWS. There is no workaround from the Identity Manager side of this integration. After any upgrade, you will want to review any tews calls for functionality loss.