Agile Requirements Designer

 View Only
  • 1.  Single Sign On (SSO) integration with CA Agile Central

    Posted Nov 20, 2017 04:02 AM
      |   view attached

    Customer is integrating ARD with CA Agile Central (AC). Access to Agile Central is Single Sign On (SSO) enabled.

    Required details on the integration between ARD & AC, incase of SSO. What are the entries to be made on AC connector option?

    Attached the error screenshot.



  • 2.  Re: Single Sign On (SSO) integration with CA Agile Central
    Best Answer

    Posted Nov 20, 2017 08:35 AM

    Hi Pratik, 

     

    I would recommend the customer open a support ticket on CA Support Online - CA Technologies so that we can investigate further.

     

    From the screenshot, it looked like the wrong URL format was being used. It should be something like this http://localhost:8095 based off of this documentation: Integrate With CA Agile Central - CA Agile Requirements Designer - 2.6 - CA Technologies Documentation.  

     

    You can enable debugging, recreate the issue, and look at the resulting log file for more information. This document outlines how to do this: How to Enable Debugging for Rally Integration with Agile Requirements Designer 

     

    This is what I found for the error message:  

     

    List of HTTP status codes - Wikipedia 

    200 OK- Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request, the response will contain an entity describing or containing the result of the action.

     

    How to Tell What HTTP Error Messages Mean 

    HTTP Status Codes 200-206 - Successful Status Codes: The HTTP status messages in the 200 series indicate that the request succeeded. In fact, 200 OK is the most common HTTP status message. This message means the server answered the request. 

     

    HTTP Status Codes 

    200 OK

    The request has succeeded. The information returned with the response is dependent on the method used in the request, for example:

    • GET an entity corresponding to the requested resource is sent in the response;
    • HEAD the entity-header fields corresponding to the requested resource are sent in the response without any message-body;
    • POST an entity describing or containing the result of the action;
    • TRACE an entity containing the request message as received by the end server.

     

    Again, it might be best to open a support case and we can post the resolution here once the case is closed. 

     

    Best regards,

    Taylor