Symantec Access Management

 View Only
  • 1.  Error creating Partnership after the installation of SP03

    Posted Feb 10, 2020 11:04 AM
    A couple of days ago we did the SP03 update on our SSO platform. Now when we try to create an association or modify an existing one, we get the following message:


    When we review the AdminUI logs, the following appears:
    2020-02-10 10:08:21,144 [ERROR] com.ca.federation.adminui.backingbean.federation.CreatePartnershipWizardBean [] - Error in onStepChange:
    2020-02-10 10:08:21,144 [ERROR] com.ca.federation.adminui.backingbean.federation.CreatePartnershipWizardBean [] - Error in onStepChange: com.ca.fedxps.api.remote.FedXPSException: com.ca.federation.client.XPSException: Failed to get the DD Reference for an Attribute, Attr = CA.FED::PartnershipBase.EnableIdentityMapping, Vendor = CA, Prod = FED, Class = PartnershipBase : CA : XPS : sm-xpssvc-00140
    at com.ca.fedxps.api.remote.FedXPSObjectStore.create(Unknown Source) ~[fedremoteapi.jar:?]
    at com.ca.fedxps.api.remote.FedXPSObjectStore.update(Unknown Source) ~[fedremoteapi.jar:?]




    Will anyone know how this problem can be corrected? Will there be any pending command to execute once the SP03 update is done?

    Thank you very much in advance.

    #casinglesignon
    #partnership
    #casinglesignon12.8


    ​​​​​​​​​​​


  • 2.  RE: Error creating Partnership after the installation of SP03
    Best Answer

    Broadcom Employee
    Posted Feb 10, 2020 10:01 PM

    Try running the following command on the policy server:

    XPSDDInstall smmaster.xdd

    This shouldn't be necessary for partnership federation to work after an upgrade, but may resolve whatever the underlying problem is.  The command will do no harm if not needed (data is not affected, only the default data definitions)  You will need to restart the policy server after running the command to reload the updated store.

    Regards,
    Pete




  • 3.  RE: Error creating Partnership after the installation of SP03

    Posted Feb 12, 2020 11:54 AM
    Thank for your Reply Peter

    Effectively i executed the  XPSDDInstall smmaster.xdd command and the other indications given in the following link to update the Policy Store. Once the Policy Servers were restarted, the problem was resolved.

    This is the link: https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/layer7-identity-and-access-management/single-sign-on/12-8-03/upgrading/in-place-upgrade/upgrade-policy-store.html


    Thank you very much for your support