[
https://issues.apache.org/jira/browse/SYNCOPE-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17708317#comment-17708317
]
ASF subversion and git services commented on SYNCOPE-1749:
----------------------------------------------------------
Commit e01d9a12851bd51750383663345c8ff1e336683e in syncope's branch
refs/heads/master from Samuel Garofalo
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=e01d9a1285 ]
[SYNCOPE-1749] Preserve Dynamic Group Membership Condition order when save from
Console (#435)
> Incorrect Dynamic Group Membership Condition save from Console
> --------------------------------------------------------------
>
> Key: SYNCOPE-1749
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1749
> Project: Syncope
> Issue Type: Bug
> Components: console
> Affects Versions: 2.1.13, 3.0.2
> Reporter: Francesco Chicchiriccò
> Assignee: Samuel Garofalo
> Priority: Major
> Fix For: 2.1.14, 3.0.3, 4.0.0
>
>
> When setting dynamic membership conditions for an existing Group as follows:
> # ATTRIBUTE, username, == , *a
> # AND, ATTRIBUTE, username, == , *b
> # AND, ATTRIBUTE, username, == , *c
> # OR, ATTRIBUTE, username, == , *d
> # OR, ATTRIBUTE, username, == , *e
> this is the FIQL resulting after save:
> {code}
> (username=~*e,(username=~*d,(username=~*c;(username=~*b;username=~*a))))
> {code}
> where ordering is evidently incorrect.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
