[
https://issues.apache.org/jira/browse/SYNCOPE-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18069076#comment-18069076
]
ASF subversion and git services commented on SYNCOPE-1957:
----------------------------------------------------------
Commit bb7f727dc7effa80c186c51b754bd12ad654bafa in syncope's branch
refs/heads/master from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=bb7f727dc7 ]
[SYNCOPE-1957] Process auxClasses changes before attributes during update
> Wrong validation triggered while updating users, groups or any objects after
> auxiliary class change
> ---------------------------------------------------------------------------------------------------
>
> Key: SYNCOPE-1957
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1957
> Project: Syncope
> Issue Type: Bug
> Components: core
> Affects Versions: 4.0.4, 4.1.0-M0
> Reporter: Andrea Patricelli
> Assignee: Francesco Chicchiriccò
> Priority: Major
> Fix For: 4.0.5, 4.1.0, 5.0.0
>
>
> * Login as admin into admin console
> * create 2 schemas
> * put both schemas in a single AnyTypeClass, for example aux1
> * create a Group and add aux1 as aux class and fill both schemas added by
> the aux class while creating.
> * remove one of the 2 schemas from AnyTypeClass aux1
> * create a second AnyTypeClass aux2 and move one schema from aux1 to aux2
> any type class, so that both contain a single schema.
> * Edit the previously created group assigning the new aux class aux2 and
> saving, an InvalidEntity error is thrown even if the schema is allowed
> (assigned by aux2 and no more by aux1), e.g. *InvalidEntity:
> InvalidPlainAttr: [schemaName] not allowed for this instance*
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
