Activation of partnership failed in AdminUI server.log

Products

• SITEMINDER

Issue/Introduction

 

When running an AdminUI, and configuring a new partnership, the partnership cannot be activated once saved.

 

The AdminUI server.log reports the error:

 

  2024-02-01 16:36:15,273 [INFO] ims.ui.ConsolePageFilter [] - dispatch=/app/ui7/index.jsp

  2024-02-01 16:36:15,305 [ERROR] com.ca.federation.adminui.backingbean.federation.PartnershipListBean [] - **ERROR** com.ca.fedxps.api.remote.FedXPSException during UI operation.

  com.ca.fedxps.api.remote.FedXPSException: Activation of partnership failed

at com.ca.federation.api.remote.FedServices.activate(Unknown Source) ~[fedremoteapi.jar:?]

at com.ca.federation.adminui.backingbean.federation.PartnershipListBean.activatePartnership(PartnershipListBean.java:2367) ~[fedmgr.jar:?]

 

That's the first time this issue occurs.

 

Cause

 

The AdminUI reports the error:

 

server.log:

  

2024-02-01 16:36:15,273 [INFO] ims.ui.ConsolePageFilter [] - dispatch=/app/ui7/index.jsp

2024-02-01 16:36:15,305 [ERROR] com.ca.federation.adminui.backingbean.federation.PartnershipListBean [] - **ERROR** com.ca.fedxps.api.remote.FedXPSException during UI operation.

com.ca.fedxps.api.remote.FedXPSException: Activation of partnership failed

at com.ca.federation.api.remote.FedServices.activate(Unknown Source) ~[fedremoteapi.jar:?]

at com.ca.federation.adminui.backingbean.federation.PartnershipListBean.activatePartnership(PartnershipListBean.java:2367) ~[fedmgr.jar:?]

 

For that action, the Policy Server reports that the SPID value is duplicated, and as such, the Partnership can't be activated:

        

smtracedefault.log

 

  [02/01/2024][16:36:15.302][16:36:15][2166114][140674364057344][CServer.cpp:1528][ThreadPool::Run][][][][][][][][][][][][][][][10.0.0.1][58806][][][][][Dequeuing a Normal Priority message, from IP 10.0.0.1 with Port No 58806. Current count is 0][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][00:00:00.000034][]

  [02/01/2024][16:36:15.304][16:36:15][2166114][140674364057344][SPPartSvc.cpp:2012][canBeActivated][][][][][][][][][][][][][][][][][][][][][LogMessage:ERROR: Existing SAML 2.0 Service Provider is already active; Name: <partnership-A> (CA.SM::SAMLv2SP@21-00041836-5af3-1f91-0000-44dsad44da4sd)][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][]

  [02/01/2024][16:36:15.304][16:36:15][2166114][140674364057344][SPPartSvc.cpp:2556][setActivated][][][][][][][][][][][][][][][][][][][][][LogMessage:ERROR: setActivated failed.][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][]

  [02/01/2024][16:36:15.304][16:36:15][2166114][140674364057344][PartnershipService.cpp:2078][PartnershipService][][][][][][][][][][][][][][][][][][][][][LogMessage:ERROR: PartnershipService failed.  Operation: 3][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][][]

 

The Partnership <partnership-B> and the Partnership <partnership-A> have the same SPID "https://sp.example.com".

 

Resolution

Ensure there's only 1 SPID with the value "https://sp.example.com" in the environment to solve the issue.