Fix (APAR):  PI82308

Status:  Fix

Release:  8.5.5.12,8.5.5.11,8.5.5.10,8.5.5.9,8.5.5.8,8.5.5.7,8.5.5.6,8.5.5.5,8.5.5.4,8.5.5.3

Operating System:  AIX,HP-UX,IBM i,Inspur K-UX,Linux,Solaris,Windows,z/OS

Supersedes Fixes:  PI23430 PI25298 PI25681 PI33449 PI37687 PI47460 PI52604 PI55697 PI56331 PI59831 PI63906 PI64573 PI64924 PI65751 PI73318 PI74857 PI75095 PI78336 PI80543 PI80549 PI80317 PI84244 PI86752 PI87354

CMVC Defect:  xxxxxx

Byte size of APAR:  3574041

Date: 2017-09-14

Abstract:  openid connect (oidc) relying party (rp) loses url fragments during the login process

Description/symptom of problem:  
PI82308 resolves the following problem:

ERROR DESCRIPTION:                                              
The OpenId Connect (OIDC) Relying Party (RP) TAI loses          
fragments in the request to a protected resource.               
                                                                
For instance, if a request is made to                           
http://abc.com/action.html#one, after login, the user will be   
redirected to http://abc.com/action.html.                       

LOCAL FIX:                                                      
NA                                                              

PROBLEM SUMMARY

USERS AFFECTED:
 IBM WebSphere Application Server and
OpenID Connect Relying Party TAI

PROBLEM DESCRIPTION:
The OIDC TAI does not handle URL
fragments properly

RECOMMENDATION:
 Install a fix pack or interim fix that
contains this APAR.

When a request is made to a resource protected by the OpenId
Connect (OIDC) Relying Party (RP), if the request contains URL
fragments, those fragments are lost during the authentication
process.
For instance, if a request is made to
http://abc.com/action.html#one, after login, the user will be
redirected to http://abc.com/action.html.

PROBLEM CONCLUSION:                                             
The OIDC TAI is updated to preserve URL fragments on requests   
made to a protected resource.                                   
                                                                
The fix for this APAR is currently targeted for inclusion in    
fix pack 8.0.0.14, 8.5.5.13, and 9.0.0.6.  Please refer to the  
Recommended Updates page for delivery information:              
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980   


Directions to apply fix:  Fix applies to Editions:
Release 8.5
_x_ Application Server (Express or BASE)
_x_ Network Deployment (ND)
__ Liberty Core
__ Edge Components
__ Developer

Install Fix to all WebSphere installations unless special instructions are included below.

Special Instructions: None

NOTE:
The user must:
* Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
* Be at V1.4.3 or newer of the Installation Manager. Certain iFixes may require a newer version of the Installation Manager and the Installation Manager will inform you during the installation process if a newer version is required.

The IBM Knowledge Center can provide details, if needed, on the use of the Installation Manager to apply the iFixes.
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp.  Shutdown WebSphere Application Server before applying the iFixes.  Restart WebSphere Application Server after applying the iFixes.

Directions to remove fix:  

The IBM Knowledge Center can provide details, if needed, on the use of the Installation Manager to remove the iFixes.
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp.  Shutdown WebSphere Application Server before removing the iFixes.  Restart WebSphere Application Server after removing the iFixes.

Directions to re-apply fix:  
1) Shutdown WebSphere Application Server.

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere Application Server.



Additional Information: