IBM Support

IJ28344: Incorrect Error message on OSLC Provider Interaction with OAuth having wrong rdf mapping

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • DESCRIPTION: Error message on OSLC interaction points to OAuth
    error with response code 500 even when this is not an issue.
    STEPS TO REPRODUCE:
    (Preparation   Add Resource Types)
    1. Go To -> Integration -> OSLC Providers
    2. Select Action -> Add/Modify Resource Types
    (a) Resource Type: MYCQ
    (b) Resource Type URI:
    http://open-services.net/ns/cm#ChangeRequest
    (c) Import the Shape document.
    (d) Save.
    (Preparation   Add OSLC Provider)
    3. Go To -> Integration -> OSLC Providers
    4. Select Action -> Insert OLSC Provider
    (a) Provider: MYCQPROVIDER
    (b) End Point: SCCDCQOAUTH
    (c) Public URI: http://cqwebserver/cqweb
    (d) Service Provider List URI:
    http://cqwebserver/cqweb/oslc/repo/9.0.0
    (e) Save.
    (Reproducing the issue - Create an OSLC Interaction)
    5. Go To -> Integration -> OSLC Providers
    6. Open MYCQPROVIDER (created at step 3, 4)
    7. Select Action -> Create OSLC Interaction
    Step 1
    (a) Interaction: INTERACTIONTEST
    (b) Interaction Type: CREATIONDIALOG
    (c) Resource Type: Key-in MYCQ (created at step 1, 2) manually
    and tab out.
    (d) ClearQuest authentication page is invoked and provide
    credential to authenticate.
    Step 2
    (e) Uncheck 'Use All Service Providers?' and select 'Service
    Provider URI'
    (f) Click Next
    Step 3
    (g) At Application field, select 'INCIDENT' from the lookup.
    (h) At Application Tab field, fill in 'relatedrec' and tab out.
    (i) Click Next
    Step 4
    (j) Click Complete
    8. Go To -> Security -> Security Groups application
    (a) Filter for MAXEVERYONE and open the record.
    (b) Go to Applications tab
    (c) Filter for Incidents and expand the record
    (d) Grant permission to 'INTERACTIONTEST' (created at step
    7(a)).
    9. Logout and login Maximo again
    10. Go To -> Service Desk -> Incidents
    (a) Open any existing Incident record
    (b) Go to Related Record tab
    (c) Click on the 'INTERACTIONTEST' button.
    RESULT: An exception is thrown in the logs for OSLC Interaction
    reporting about OAuth error with response code 500.
    EXPECTED RESULT: Error message should not generically point to
    OAuth issue and suggest more for checking the logs. Example- to
    enable maximo.oslc logger to DEBUG and analyse the logs.
    REPORTED IN VERSION:
    Tivoli's process automation engine 7.6.1.0
    IBM TPAE Integration Framework 7.6.1.0
    IBM Control Desk 7.6.1.0319
    

Local fix

  • N/A
    

Problem summary

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package: release\fix pack for Release 7.6.1.3 Product
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ28344

  • Reported component name

    INTEGRATION

  • Reported component ID

    5724R46I1

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-09-24

  • Closed date

    2022-09-13

  • Last modified date

    2022-09-13

  • 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

    INTEGRATION

  • Fixed component ID

    5724R46I1

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
14 September 2022