Features

API Changes

The schema validation was completely reworked due to its monolithic structure as single class it was hard to maintain and errors were hard to be found. This change also results in changed error messages.
If an endpoint requires authentication and the developer missed to add the Authorization interface implementation to the ResourceEndpoint a log-warning will be written on each request to the specific resource-type-endpoint.
Changed the log level of several messages
Add small performance boost for create and update requests
The schemas-attribute is now optional in requests:
- In order to simplify the usage with e.g. javascript frameworks like React I removed the necessity in requests to add the schemas-attribute. It is now determined automatically by the API based on the endpoint that is accessed. Also resource-extensions are determined automatically
Added a new reference Type URL
- RFC7643 defines 3 referenceTypes [URI, EXTERNAL, RESOURCE]. I allowed myself to add a fourth referenceType [URL] that checks that the provided reference is a URL
Authentication-failure is no longer logged as an error. The log message will now be printed on debug level. An administrator does not need to be informed about any failed authentication but should be able to trace it.

During rebuilding of the schema validation implementation some minor uncritical bugs were detected and fixed
the startIndex will only be handled by the API if the auto-filtering feature is enabled. It clashes otherwise with the intention of the developer who already handled the startIndex
A bug was fixed that caused the ScimRequestBuilder on client side in some cases to ignore the preconfigured basic-authentication details.
If the client sends illegal values for startIndex or count in the request an appropriate error message with status 400 (BAD_REQUEST) will be returned

the build sources are now delomboked during release to prevent a byte and source code mismatch during debugging in the IDE