IBM Support

PH58888: RSAD 9.7.1 REST TRANSFORMATIONS DO NOT COMPLY WITH OPENAPI3 SPECIFICATION

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

  • When using the REST-to-OpenAPI and OpenAPI-to-REST
    transformations in Rational Software Architect Designer (RSAD)
    9.7.1, you may find that you are unable to generate an oAuth3
    specification Swagger document.
    
    According to the OpenAPI3 specification here:
    
              https://swagger.io/specification/v3/#oauth-flow-object
    
    There are 4 possible oAuth flow types that can be set to the
    Security scheme object as follows:
    
    1. Implicit
    2. Password
    3. ClientCredentials (previously Application)
    4. AuthorizationCode (previously AccessCode)
    
    However, when using the above-mentioned transformations in RSAD
    9.7.1, only the implicit type is supported as default OAuth2;
    the remaining selections are ignored. This is because these
    other types are not being handled properly during the
    transformations; the current RSAD OpenAPISecurityOAuth2
    stereotype flow parameter does not support these values and
    generated structures.
    

Local fix

  • There is no workaround at this time.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * -                                                            *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * REST-to-OpenAPI transformation does not generate supported   *
    * flow types in OAuth2 security schema object. It always       *
    * generates the Implicit flow type only.                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • REST-to-OpenAPI transformation now generates appropriate flow
    type in OAuth2 security schema object based on user selection in
    the model.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH58888

  • Reported component name

    SW ARCHITECT WI

  • Reported component ID

    5724I7001

  • Reported release

    971

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-12-20

  • Closed date

    2024-05-02

  • Last modified date

    2024-05-02

  • 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

    SW ARCHITECT WI

  • Fixed component ID

    5724I7001

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSYKBQ","label":"Rational Software Architect Designer for = WebSphere Software"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"971","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]

Document Information

Modified date:
02 May 2024