Importing IDP metadata giving error. Error: Exception occurred: Unknown : CA : XPS : sm-xobfed-00140

Products

• CA Single Sign-On
• SITEMINDER
• CA Single Sign On Secure Proxy Server (SiteMinder)
• CA Single Sign On Federation (SiteMinder)

Issue/Introduction

------ Issue:

Importing IDP metadata giving error.

Error observed on the AdminUI screen:

Exception occurred: Unknown : CA : XPS : sm-xobfed-00140

----- Steps:

- Access the above mentioned AdminUI.

- Go to Federation --> Partnership --> Entities

- Click on Import Metadata

- Select the attached metadata file (CA - Downer-pDXC.xml (METADATA File))

- Select " Remote Entity " and " Create New " options

- Click on Next

- You will see the Exception occurred: Unknown : CA : XPS : sm-xobfed-00140 message on the AdminUI server.

- Reference Snippet:




------ Log Analysis:

- SMPS.log:

[JavaCallService.cpp:325][PerformService][ERROR][sm-xobfed-00140] Exception occurred: Unknown

- smtracedefault.log:

[JavaCallService.cpp:325][PerformService][][][][][][][][][][][][][][][][][][][][][][][][][][][LogMessage:ERROR: Exception occurred: Unknown][][][][][][][][][]

 

Environment

Environment:  Applicable to Policy Server release: R12.8 SP6
Component: SMPLC

Resolution

This is a known issue in the 12.8 SP6 release. If you are experiencing this issue using the 12.8 SP6 release and need a solution more quickly than upgrading to 12.8.7 or later, apply the attached patch.

Also, the Internal SE Engineering team confirmed that this PATCH is in the 12.8 SP7 release.

Additional Information

See attached patch named fedserver.jar.

This was developed on top of 12.8.6 GA release

Follow deployment instructions given below:

1. Stop policy Server if running
2. Take backup of fedserver.jar from <siteminder..>\bin\jars folder  to safe location.
   Note : Do not rename original fedserver.jar leaving extention as .jar in the same location. Engineering recommends to remove the fedserver.jar from <siteminder..>\bin\jars folder
3. Place attached fedserver.jar in <siteminder..>\bin\jars folder
4. Start Policy Server
5. Run use case again