Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
the group and group-member sync code in the DefaultSyncContext twice catches ClassCastException and swallows exception situations, where a user is found, when actually a Group was expected.
i would suggest to
- explicitly test the assumption wrt ExternalIdentity being a group (instead of waiting for the exception)
- make use of UserManager.getAuthorizable(String, Class) to explicitly retrieve a Group with a given ID, when this is actually expected. This method will throws an {{AuthorizableTypeException if there exists a User with that ID as thus properly raise the unexpected behavior instead of swallowing with a log-warning.
Attachments
Attachments
Issue Links
- is cloned by
-
OAK-3563 Improve DefaultSyncContext
- Closed