Clarity

  • 1.  Ping Access and CA PPM

    Posted Jun 14, 2018 08:59 AM

    Does anyone have experience / knowledge about Ping Access and CA PPM scheduling tools such a OWB or MSP which both using Schedule Connect component?

     

    We are in the process of moving away from SiteMinder product for SSO and implementing Ping Access Identity Management.

     

    Currently we have configured and installed successfully in our lower DEV environment Ping Access to handle SSO and it works fine for CA PPM access but does not work .



  • 2.  Re: Ping Access and CA PPM

    Broadcom Employee
    Posted Jun 15, 2018 05:32 PM

    Hi Allen,

     

    None of our non-browser clients (MSP, Open Workbench, XOG) are SSO aware.  This means that urls related to these clients need to be unprotected.  Please look at the information on how to set up Siteminder to work with PPM.  You will need to set up equivalent settings under Ping Access in order to get a non-supported SSO product such as Ping Access to work with our product.

     

    Here is a link to that documentation for 15.2:

    https://docops.ca.com/ca-ppm/15-2/en/add-ins-and-integrations/integrate-ca-ppm-with-ca-single-sign-on-sso 

    If I have picked the wrong version of PPM, you can change the version under the Version drop down at the top of the page.

     

    I hope you find this information helpful.

     

    Jeanne Gaskill (CA)



  • 3.  Re: Ping Access and CA PPM

    Posted Jun 21, 2018 06:41 AM

    Allen,

     

    We have performed work in integrating CA PPM and PF for a client and the answer to your problem depends on how you actually do it and the nature of the issue.  You can look at Integrating CA PPM with Ping Federate for Single Sign-On - Pemari  for info on how we did it.

     

    But for OWB, the MSP Connector and XOG the only endpoints we protected were /niku/app, /niku/nu and /ppm/rest/*.  it is then possible to launch OWB/MSP via the browser links in CA PPM and for them to use the browser session, use XOG since xog uses /niku/xog and this in not protected.  As Jeanne stated above, OWB, XOG and the MSP connector are desktop clients and not SSO aware so for xog you'll always need to logon, for the OWB and MSP Connectors, launching via browser will be fine but you'll be presented with a logon on session timeout or if launching them directly on the client PC.

     

    Andy