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

Fix packs for DataPower Integration Appliance version 6.0
Fix packs for DataPower Service Gateway version 6.0
Fix packs for DataPower Service Gateway version 6.0.1
Fix packs for DataPower Integration Appliance version 6.0.1
Fix packs for DataPower Service Gateway version 7.0
Fix packs for DataPower Integration Appliance version 7.0
Fix packs for DataPower Gateway version 7.1

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

• Fix is available in 6.0.0.16, 6.0.1.12, 7.0.0.9, 7.1.0.6
  and 7.2.0.0.
  
  For a list of the latest fix packs available, please see:
  http://www-01.ibm.com/support/docview.wss?uid=swg21237631
  

Temporary fix

Comments

APAR Information

• 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