You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/Libraries/java/changelog.md
+14-5Lines changed: 14 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,13 @@
1
1
# Release Notes for AMS Client Library Java
2
2
3
-
## 4.0.0 - 4.0.5*
3
+
## Version 4
4
+
5
+
### 4.0.6
6
+
7
+
- Fix: Read Number constants from DCN as `Double` instead of `Long/Int` to avoid runtime errors when comparing with `Double` attribute input
8
+
- Fix `AmsCapAutoConfiguration`: Use @Order(-100) for `AmsUserInfoProvider` bean to make sure it runs late in the `UserInfoProvider` chain. For example, this fixes incompatibilities with DwcUserInfoProvider which must run before the `AmsUserInfoProvider` to extract user information from the token.
9
+
10
+
### 4.0.0 - 4.0.5*
4
11
5
12
Version 4 drastically changes the core API to streamline it with the Node.js library which received positive feedback since it introduced the same changes.
6
13
@@ -17,7 +24,7 @@ during application start. As a result, the authorization checks themselves remai
17
24
::: tip ZTIS Auto-Configuration
18
25
There is out-of-the-box support for ZTIS service bindings via the Spring Boot starters.
19
26
:::
20
-
- Domain-Specific `Authorizations` by [wrapping](https://github.com/SAP-samples/ams-samples-java/blob/new_lib_v4/ams-javalin-shopping/src/main/java/com/sap/cloud/security/ams/samples/auth/AuthHandler.java#L68)`Authorizations` objects with [domain-specific methods](https://github.com/SAP-samples/ams-samples-java/blob/new_lib_v4/ams-javalin-shopping/src/main/java/com/sap/cloud/security/ams/samples/auth/ShoppingAuthorizations.java#L27-L46) for [better readability](https://github.com/SAP-samples/ams-samples-java/blob/new_lib_v4/ams-javalin-shopping/src/main/java/com/sap/cloud/security/ams/samples/service/OrdersService.java#L151-L153) and reusability of authorization checks across your application.
27
+
- Domain-Specific `Authorizations` by [wrapping](https://github.com/SAP-samples/ams-samples-java/blob/main/ams-javalin-shopping/src/main/java/com/sap/cloud/security/ams/samples/auth/AuthHandler.java#L68)`Authorizations` objects with [domain-specific methods](https://github.com/SAP-samples/ams-samples-java/blob/main/ams-javalin-shopping/src/main/java/com/sap/cloud/security/ams/samples/auth/ShoppingAuthorizations.java#L27-L46) for [better readability](https://github.com/SAP-samples/ams-samples-java/blob/main/ams-javalin-shopping/src/main/java/com/sap/cloud/security/ams/samples/service/OrdersService.java#L151-L153) and reusability of authorization checks across your application.
21
28
::: tip CdsAuthorizations
22
29
The CAP Spring Boot starter already wraps the standard `Authorizations` in a `CdsAuthorizations` adapter that provides CAP-specific methods for role checks.
23
30
:::
@@ -51,17 +58,19 @@ Our performance tests have indicated that the performance impact of authorizatio
51
58
52
59
For example, for both library versions, the request latency for a localhost CAP OData endpoint with instance-based authorization filters was `<= 5ms` of which most of the time was likely spent on database and network handling instead of the AMS library.
53
60
54
-
## 3.8.0
61
+
## Version 3
62
+
63
+
### 3.8.0
55
64
56
65
- This release removes the dependencies from `com.sap.cloud.security.ams.dcl` artifacts. All required classes,
57
66
interfaces, etc., are now part of the `jakarta-ams` module using the same packages. So, everything should continue
58
67
to work without any changes. Please remove any direct dependencies on `com.sap.cloud.security.ams.dcl` artifacts.
59
68
60
-
## 3.7.0
69
+
###3.7.0
61
70
62
71
- Maintenance release with updated dependencies and fixes for the Maven Central release process.
63
72
64
-
## 3.6.0
73
+
###3.6.0
65
74
66
75
- The property `cds.security.mock.enabled` is now used to enable the mock users in the
@@ -201,10 +223,10 @@ Replace the DCL output directory with the new default output directory for AMS D
201
223
202
224
### CAP Java Configuration
203
225
204
-
- Remove test sources property from `application.yaml`:
226
+
- Remove test sources property from `application.yaml`. It is no longer used:
205
227
206
228
```yaml
207
-
cds:
229
+
cds:# [!code --:5]
208
230
security:
209
231
authorization:
210
232
ams:
@@ -217,5 +239,5 @@ In v4, the existence of `spring-boot-starter-ams-cap-test` on the classpath dete
217
239
218
240
### Spring Security Tests
219
241
220
-
The `MockOidcTokenRequestPostProcessor.userWithPolicies` from `jakarta-ams-test` has been removed because the real AMS production code can now be tested.
242
+
The `MockOidcTokenRequestPostProcessor.userWithPolicies` from `jakarta-ams-test` has been removed because now, the full AMS production code can be tested including the real `AuthorizationProvider`.
221
243
It requires the definition of a [policy assignments](/Authorization/Testing#assigning-policies-to-mocked-users) map from which AMS determines the used policies based on the `app_tid` and `scim_id` claims of the token, and for advanced token flows: other claims as needed.
0 commit comments