IBM Support

IT09129: CUSTOM OAUTH PROCESS DOES NOT PROVIDE SPECIFIC ERROR_ID IF VERIFY-AZ-REQUEST FAILS

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Custom-oauth-client.xsl is invoked with operation
    verify-az-request to check for various conditions (i.e is the
    parameter scope valid, does the client state exist, etc.)
    
    If one of the checks fails, DataPower sends the redirect to the
    client with the following query parameters:
    
    error=invalid_request&error_description=<text>&state=<clientStat
    e>
    
    DataPower should indicate the specific error_id, such as
    "invalid_scope", instead of generic error_id of
    "invalid_request".
    

Local fix

Problem summary

  • OAuth authorization request error response messages may not
    contain an error id attribute.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT09129

  • Reported component name

    DATAPOWER

  • Reported component ID

    DP1234567

  • Reported release

    720

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-05-27

  • Closed date

    2015-08-20

  • Last modified date

    2015-09-01

  • 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

    DATAPOWER

  • Fixed component ID

    DP1234567

Applicable component levels

  • R600 PSY

       UP

  • R601 PSY

       UP

  • R700 PSY

       UP

  • R710 PSY

       UP

  • R720 PSY

       UP



Document information

More support for: IBM DataPower Gateways
General

Software version: 7.2

Reference #: IT09129

Modified date: 01 September 2015