Fix (APAR):  PI36211

Status:  Fix

Release:  7.0.0.37,7.0.0.35,7.0.0.33

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

Supersedes Fixes:  PI29634

CMVC Defect:  xxxxxx

Byte size of APAR:  77611

Date: 2015-03-16

Abstract:  Confidential for Security Integrity ifix for OAuth in the full profile

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

ERROR DESCRIPTION:
Confidential for Security Integrity ifix for OAuth in the full profile.

LOCAL FIX:                                                      

PROBLEM SUMMARY:
Confidential for Security Integrity ifix for OAuth in the full profile.

PROBLEM CONCLUSION:
Confidential for Security Integrity ifix.


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

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

Special Instructions: 
When a fix pack containing this APAR is installed, the fix will not be active until the installed OAuth ear, WebSphereOauth20SP.ear, is updated from the (WAS_HOME)/installableApps directory.                     

NOTE:
The user must:
* Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
* Be at V7.0.0.0 or newer of the Update Installer. Certain iFixes may require a newer version of the Update Installer and the Update Installer will inform you during the installation process if a newer version is required. This can be checked by reviewing the level of the Update Installer in file <was_root>/updateinstaller/version.txt.

The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

1) If your iFix is delivered as a single file with a .pak extension, Copy the .pak file directly to the maintenance directory. If your iFix is delivered as a single file with a .zip extension, unzip the file into the maintenance directory.

2) Shutdown WebSphere Application Server.
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to.

3) For IBM i users, use the update command to install and uninstall the interim fix.  The IBM Information Center can provide additional details, if needed, on the use of this command.
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-iseries&topic=rins_update.
For non-IBM i users, launch the Update Installer and click the Next button on the Welcome page.

4) Enter the directory path of the installation location of the WebSphere product you want to update, and click the Next button.

5) Select the "Install maintenance package" operation and click the Next button.

6) Enter the directory path of your maintenance directory where you have the maintenance packages (.pak files) and click the Next button.

7) The Available Maintenance Package to Install page should list all maintenance packages (.pak files) that it finds in the directory path provided in the previous step.  The Update Installer will select the correct maintenance packages based on your system configuration and will not allow an invalid combination to be installed.  Please keep the Update Installer recommendations and click the Next button and continue with the installation of the maintenance package.  To determine why some maintenance packages have been identified as not applicable, see description in log found in <UPDI_root>/logs/tmp*/updatelogs.txt

8) For all platforms except Windows. In pre-install summary panel, use the "verify permission" feature to verify the user has permissions to apply updates to files associated with the selected maintenance.  Correct any file permissions before clicking next to start the install.

9) Restart WebSphere Application Server.


Directions to remove fix:  
NOTE:
* The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED
* DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED
* YOU MAY REAPPLY ANY REMOVED FIX

Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied.

1) Shutdown WebSphere Application Server.
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against.

2) Start Update Installer

3) Enter the installation location of the WebSphere product you want to remove the fix.

4) Select  "Uninstall maintenance package" operation.

5) Enter the file name of the maintenance package to uninstall (PKxxxxx.pak).

6) UnInstall maintenance package.

7) Restart WebSphere

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: