Fixes are available
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
PI96508: OIDC v1.05; OIDC RP may not connect to token endpoint due to SSL handshake failure
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
PH08804: OIDC v1.1.0; OIDC RP default identifiers are not available when customs are configured
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
PH13175: OIDC v1.2.0; OIDC RP tokens are not revoked when sessions are evicted from the cache
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
PH29099: OIDC v1.3.1; OIDC RP: ClassNotFoundException for JsonUtil$DupeKeyDisallowingLinkedHashMap
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
PH39666: OIDC v1.3.2; OIDC RP: Initial login might fail when the OIDC stateId contains special characters
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
When an unauthorized user accesses a resourced protected by the WASt OIDC RP, a cookie of the form OIDSTATEID_X, where X is a randomly-generated string unique to the login state. In certain situations, the browser will not delete the cookie after the subsequent login, causing an accumulation of cookies which may render future requests invalid due to the size of the HTTP request header within which the cookies are sent.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server users of * * OpenID Connect * **************************************************************** * PROBLEM DESCRIPTION: OIDC RP cookies can accumulate in * * browser and cause problems * **************************************************************** * RECOMMENDATION: Install a fix pack that includes this * * APAR. * **************************************************************** The OIDC RP generates a many cookies if the user performs many logins. Even though the cookies are deleted at the end of the process, some browsers don't really remove the cookies until the browser is stopped and it causes problems for applications.
Problem conclusion
The OpenID Connect Relying Party (RP) in the full profile uses a unique cookie to store request data for each request to protected resources. When the request flow is complete, the cookie is deleted. Since some browsers do not fully delete deleted cookies until the browser is restarted, the cookies can build up and cause unexpected behavior in the browser. The OpenID Connect RP in the full profile is updated to reduce the number of cookies that are used to one per configured protected resource. The following OIDC TAI global custom properties are added: useStateCookies default=true By default, the run time uses both local storage and browser cookies to store request data when a request is redirected to the OP. When this property is false, the OIDC TAI will not use browser cookies; only local storage will be used. maxCookieSize default=4093, minimum=500, maximum=4093 Maximum cookie size that the run time will create. At runtime, if the data to be written is larger than the value for this property, the request will be rejected. This property applies to, and can be overridden by both maxStateCookieSize and provider.<id>.postParameterCookieSize. The value must be between [500] and [4093]. maxStateCookieSize default=4093, minimum=500, maximum=4093 Maximum state cookie size that the run time will create. At runtime, if the data to be written is larger than the value for this property, the request will be rejected. This property will override the value set for maxCookieSize for state cookies. The value must be between [500] and [4093]. useUniqueStateCookies default=false When this property is set to true, instead of using a single OIDCSTATE cookie for all requests, each request uses a new OIDCSTATE cookie. The fix for this APAR is currently targeted for inclusion in fix pack 8.0.0.14, 8.5.5.12, and 9.0.0.4. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI73318
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-12-06
Closed date
2017-03-09
Last modified date
2017-03-10
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R800 PSY
UP
Document Information
Modified date:
04 May 2022