Symantec Access Management

  • 1.  Federation Metadata URL

    Posted 01-08-2015 06:28 PM

    Hello all,

     

    We’re doing a POC to integrate SiteMinder and CRM through Federation, so we’re using the WS-Fed method.

    One of the steps is to provide for the CRM team an URL that they’ll input in their application to recovery the partnership configuration (Federation Metadata).

    It is stated in the bookshelf that the url is http://server:port/affwebservices/public/FederationMetadata/partnership_name, however I’m not able to open that, I receive a 404 error.

    Anyone knows what I'm missing here?

     

    Thanks,

    Adami



  • 2.  Re: Federation Metadata URL

    Posted 03-13-2015 10:16 AM

    Anyone able to assist with this question?

     

    Thank you

     

    Wellington Adami wrote:

     

    Hello all,

     

    We’re doing a POC to integrate SiteMinder and CRM through Federation, so we’re using the WS-Fed method.

    One of the steps is to provide for the CRM team an URL that they’ll input in their application to recovery the partnership configuration (Federation Metadata).

    It is stated in the bookshelf that the url is http://server:port/affwebservices/public/FederationMetadata/partnership_name, however I’m not able to open that, I receive a 404 error.

    Anyone knows what I'm missing here?

     

    Thanks,

    Adami



  • 3.  Re: Federation Metadata URL

    Posted 03-16-2015 02:54 PM

    Adami

     

    Do you have a WA and WAOP deployed + Configured with the SiteMinder Policy Server infrastructure?

     

    The URL http://FQDN/affwebservices/public/FederationMetadata/partnership_name is the WAOP resource. I am assuming the WebAgent-WebServer hasn't been configured correctly to proxy the request to WAOP-ApplicationServer.

     

    Also do you have the Entities and Partnership created in WAM UI?

     

     

    Regards

     

    Hubert



  • 4.  Re: Federation Metadata URL

    Posted 06-01-2015 03:30 PM

    Sorry for the late reply.

    The problem was that the customer is using SiteMinder 12.5, which lacks a lot of WS-FED functionalities compared to 12.52 and the guide was based on the last one.

    So, we had to change the plans and configured the partnership as SAML2 IDP - SP.