IBM Support

PI83784: UNABLE TO AUTHENTICATE TO DOORS/CLM FROM CQWEB AFTER CANCELLING LOGIN

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Having cancelled a log in to DOORS, users cannot authenticate
    again unless they log off from the CQWeb session.
    This issue happens the context of CQ-DOORS integration. When a
    user logs in to CQWeb and starts an action that requires
    authentication to DOORS (DWA) such as creating a link to a
    requirement or hovering over an existing link to a requirement,
    the DOORS (DWA) login dialog box appears. If the user cancels
    the login, by closing the window (there is no cancel button)
    then it will not be possible to perform any further action that
    requires access to DOORS, as the dialog box is not offered to
    the user any more. The user needs to log out from CQWeb and log
    in again to be able to authenticate to DOORS.
    
    This behavior seems not to be limited to DOORS integration. CLM
    integration behaves in the same way.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ClearQuest Web                                               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * If a user cancels the DOORS, RTC, or any other OSLC data     *
    * provider login while viewing or accessing an OSLC link or    *
    * data, they are not asked to login again during the current   *
    * ClearQuest Web session.  It becomes necessary to log out and *
    * back in to access the linked data.                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • A fix is available in ClearQuest 9.0.1.3.
    If the user cancels login of the OSLC data provider and then
    tries to view that data again, they will be asked again to
    authenticate without having to log out of ClearQuest.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI83784

  • Reported component name

    CLEARQUEST WIN

  • Reported component ID

    5724G3600

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-06-29

  • Closed date

    2018-05-09

  • Last modified date

    2018-05-09

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    CLEARQUEST WIN

  • Fixed component ID

    5724G3600

Applicable component levels

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSSH5A","label":"Rational ClearQuest"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 October 2021