[x] Feature
[x] Refactoring (no functional changes, no API changes)
What Is the Current Behavior?
The encoding of the resource IDs like the login email for ICM REST requests is done in the encodeResourceID function with a double encoding mechanism for ICM 11.
Not all of the resource IDs are encoded.
What Is the New Behavior?
In ICM 12 a different encoding is required.
That's why there is a new feature toggle legacyEncoding that has to be switched on if an ICM 11 or lower is used.
The encodeResourceID function is moved to the api.service method encodeResourceId.
All resource IDs are encoded.
PR Type
[x] Feature [x] Refactoring (no functional changes, no API changes)
What Is the Current Behavior?
The encoding of the resource IDs like the login email for ICM REST requests is done in the
encodeResourceIDfunction with a double encoding mechanism for ICM 11. Not all of the resource IDs are encoded.What Is the New Behavior?
In ICM 12 a different encoding is required. That's why there is a new feature toggle
legacyEncodingthat has to be switched on if an ICM 11 or lower is used. TheencodeResourceIDfunction is moved to theapi.servicemethodencodeResourceId. All resource IDs are encoded.Does this PR Introduce a Breaking Change?
[x] Yes - See migration guide for instructions.
Other Information
AB#98843