Releases: SAP/cloud-security-services-integration-library
Version 2.17.1
Dependency upgrades
- Bump spring.boot.version from 2.7.17 to 2.7.18
Version 3.3.0
-
[java-security-test]
⚠️ Breaking Change To validate mocked XSUAA tokens issued by java-security-test module, theuaadomainproperty of the service configuration must now include the port of the Wiremock server.
Likewise for validating IAS tokens, the trusteddomainsarray of the service configuration also needs to include the Wiremock URL including the port.
The full wiremock URL is available viaSecurityTestContext#getWireMockServer#baseUrl.Note: If you are building your configuration via
SecurityTestContext#getOAuth2ServiceConfigurationBuilderFromFile, this will already be preconfigured correctly, but you must not overwrite these properties with only "localhost". -
[java-security]
- [XSUAA/IAS] Adapt optimized server API
-
[spring-xsuaa]
- Adapt optimized server API
Version 2.17.0
java-security-test module you might need to adjust the uaadomain in the service configuration with a port where the wiremock token key server is running on. e.g. it should be changed from localhost --> http://localhost:XXXX (you can access wiremock token key server address using testRule.getWiremockServer().baseUrl())
- [java-security]
- [XSUAA/IAS] Adapt optimized server API
- [spring-xsuaa]
- Adapt optimized server API
Version 2.16.0
- [env]
- add Environment#getServiceConfigurationsAsList to retrieve all service configurations as lists mapped by service (XSUAA/IAS)
- [spring-security]
- IdentityServicesPropertySourceFactory now populates Spring properties with ALL Xsuaa configurations found in the environment instead of only one (arbitrary) configuration of service plan 'application' and one (optional, arbitrary) additional one of service plan 'broker'.
- XsuaaServiceConfigurations#getConfigurations now contains ALL Xsuaa configurations found as a result of the previous change
- HybridIdentityServicesAutoConfiguration was adjusted for backward compatibility to still create a JwtDecoder that uses the same XSUAA configurations as before for token validation (one of plan 'application' and an optional one of plan 'broker')
Dependency upgrades
- Bump spring.security.version from 5.8.7 to 5.8.8
- Bump spring.boot.version from 2.7.16 to 2.7.17
- Bump log4j2 from 2.20.0 to 2.21.1
- Bump com.sap.cloud.environment.servicebinding from 0.10.0 to 0.10.1
- Bump commons-io from 2.14.0 to 2.15.0
Version 2.15.0
🔥 Hot fix for the CVE-2023-5072
- [java-security]
- add x-azp header to IAS JWKS fetching and adjust JWKS cache key
OAuth2TokenKeyServiceandOAuth2TokenKeyServiceWithCache- Refactor API to use generic Map instead of explicit IAS-specific parameters
Dependency upgrades
- Bump org.json.version from 20230618 to 20231013
- Bump spring.security.version from 5.8.6 to 5.8.7
- Bump spring.boot.version from 2.7.15 to 2.7.16
- Bump spring.core.version from 5.3.29 to 5.3.30
- Bump reactor-core from 3.4.32 to 3.4.33
- Bump com.sap.cloud.environment.servicebinding 0.9.0 to 0.10.0
- Bump commons-io from 2.13.0 to 2.14.0
Version 3.2.1
🔥 Hot fix for the CVE-2023-5072
Dependency upgrades
- Bump spring.boot.version from 3.1.4 to 3.1.5
- Bump log4j2.version from 2.20.0 to 2.21.0
- Bump spring.security.version from 6.1.4 to 6.1.5
- Bump org.json:json from 20230618 to 20231013
Version 3.2.0
- [java-security]
- add
x-azpheader to IAS JWKS fetching - adjust JWKS cache key for OAuth2TokenKeyService and OAuth2TokenKeyServiceWithCache
- Refactor API to use generic Map instead of explicit IAS-specific parameters
- add
Dependency upgrades
- Bump io.projectreactor:reactor-core from 3.5.9 to 3.5.11
- Bump spring.core.version from 6.0.11 to 6.0.13
- Bump spring.security.version from 6.1.3 to 6.1.4
- Bump commons-io:commons-io from 2.13.0 to 2.14.0
- Bump com.sap.cloud.environment.servicebinding from 0.9.0 to 0.10.0
- Bump spring.boot.version from 3.1.3 to 3.1.4
- Bump slf4j.api.version from 2.0.7 to 2.0.9
Version 3.1.3
- [java-security]
- Fixes NPE when accessing
XsuaaToken.getPrincipal()andgrantTypeis null (#1261)
- Fixes NPE when accessing
- [token-client]
- fixes JWKs fetch from identity service issue when
app_tidis not present in the token - theX-app_tidandX-client_idheaders are only added when both values are available. DefaultOAuth2TokenService- fixes issue when in case of unsuccessful token fetch
OAuth2ServiceException.withHeaders()headers field were filled with only one entry containing all headers as a string
- fixes issue when in case of unsuccessful token fetch
DefaultOAuth2TokenKeyServiceandSpringOAuth2TokenKeyService- improved error handling
OAuth2ServiceExceptionthat's thrown status code != 200 case doesn't get swallowed- fixes
OAuth2ServiceException.withHeaders()semantically incorrect behavior when headers were filled with request headers instead of response headers OAuth2ServiceExceptiongenerated by unsuccessful JWKs fetch contains request headers as well
- improved error handling
OAuth2ServiceExceptionupdated header message - contains nowResponse Headersinstead ofHeaders
- fixes JWKs fetch from identity service issue when
Dependency upgrades
- Bump spring.security.version from 6.1.2 to 6.1.3
- Bump spring.boot.version from 3.1.2 to 3.1.3
Version 2.14.2
- [java-security]
- Fixes NPE when accessing
XsuaaToken.getPrincipal()andgrantTypeis null (#1261)
- Fixes NPE when accessing
- [token-client]
- fixes JWKs fetch from identity service issue when
app_tidis not present in the token - theX-app_tidandX-client_idheaders are only added when both values are available. DefaultOAuth2TokenService- fixes issue when in case of unsuccessful token fetch
OAuth2ServiceException.withHeaders()headers field were filled with only one entry containing all headers as a string
- fixes issue when in case of unsuccessful token fetch
DefaultOAuth2TokenKeyServiceandSpringOAuth2TokenKeyService- improved error handling
OAuth2ServiceExceptionthat's thrown status code != 200 case doesn't get swallowed- fixes
OAuth2ServiceException.withHeaders()semantically incorrect behavior when headers were filled with request headers instead of response headers OAuth2ServiceExceptiongenerated by unsuccessful JWKs fetch contains request headers as well
- improved error handling
OAuth2ServiceExceptionupdated header message - contains nowResponse Headersinstead ofHeaders
- fixes JWKs fetch from identity service issue when
Dependency upgrades
- Bump spring.security.version from 5.8.5 to 5.8.6
- Bump spring.boot.version from 2.7.14 to 2.7.15
- Bump reactor-core from 3.4.31 to 3.4.32
Version 3.1.2
- [token-client]
OAuth2ServiceExceptionhas been extended with getter methodgetHeaders()that gives the access to failed request's response headersXsuaaOAuth2TokenServiceandDefaultOAuth2TokenServiceadd the response headers and status code to the thrownOAuth2ServiceException