Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Fix incorrect NonNull annotations in API

Description

Comments are used to track all the fixed incorrect usages of @Nonnull and @Nullable annotations.

Environment

None

Activity

Henri MikkonenMarch 27, 2024 at 4:17 PM

OIDCAuthenticationResponseContext.setAccessToken(..) involving the Scope parameter had wrong annotation for the parameter. It was fixed from @Nonnull into @Nullable. Fixed in ab81c93860045020bb238005ad562ccf5d8349c9.

RefreshTokenClaimsSet.getChainExp() return annotation changed from @Nonnull into @Nullable. The referencing code was already checking the null case. Fixed in 0223696c53d76917379752136236ecc85001fdee.

TokenClaimsSet: various getters had @Nonnull annotation even though it wasn’t really enforced. Now they’re enforced via Constraint.isNotNull(), so a ConstraintViolationException is thrown if they’re null. Fixed in 0223696c53d76917379752136236ecc85001fdee.

Completed

Details

Assignee

Reporter

Components

Fix versions

Created March 27, 2024 at 3:27 PM
Updated April 11, 2024 at 9:18 AM
Resolved April 11, 2024 at 9:18 AM

Flag notifications