[jira] [Updated] (SYNCOPE-1806) Overlapping dynamic realms don't get updated
[ https://issues.apache.org/jira/browse/SYNCOPE-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1806: Affects Version/s: 2.1.13 (was: 2.1.14) > Overlapping dynamic realms don't get updated > > > Key: SYNCOPE-1806 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1806 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.1.13, 3.0.6 >Reporter: federico brignola >Priority: Minor > Attachments: docker-compose.yml > > > When two or more dynamic realms have overlapping conditions, Users, Groups > and AnyObjects are not added to all the matching realms but only to the first > one. > > Steps to reproduce: > # run the following docker-compose environment > # create a user "user1" with email "us...@example.com" > # create a dynamic realm "dynr1" with condition "USER Dynamic Condition > [ATTRIBUTE email NOT NULL]" > # create another dynamic realm "dynr2" with the same condition of "dynr1" > # // Check that both dynamic realms contain the user "user1" > # create a new user "user2" with email "us...@example.com" > # // Check that only the realm "dynr1" contains the user "user2" while the > other doesn't -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SYNCOPE-1806) Overlapping dynamic realms don't get updated
[ https://issues.apache.org/jira/browse/SYNCOPE-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1806: Fix Version/s: 3.0.7 4.0.0 > Overlapping dynamic realms don't get updated > > > Key: SYNCOPE-1806 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1806 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.1.13, 3.0.6 >Reporter: federico brignola >Priority: Minor > Fix For: 3.0.7, 4.0.0 > > Attachments: docker-compose.yml > > > When two or more dynamic realms have overlapping conditions, Users, Groups > and AnyObjects are not added to all the matching realms but only to the first > one. > > Steps to reproduce: > # run the following docker-compose environment > # create a user "user1" with email "us...@example.com" > # create a dynamic realm "dynr1" with condition "USER Dynamic Condition > [ATTRIBUTE email NOT NULL]" > # create another dynamic realm "dynr2" with the same condition of "dynr1" > # // Check that both dynamic realms contain the user "user1" > # create a new user "user2" with email "us...@example.com" > # // Check that only the realm "dynr1" contains the user "user2" while the > other doesn't -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] [SYNCOPE-1804] Introducing syncope-core-persistence-neo4j [syncope]
ilgrosso opened a new pull request, #628: URL: https://github.com/apache/syncope/pull/628 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@syncope.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (SYNCOPE-1806) Overlapping dynamic realms don't get updated
federico brignola created SYNCOPE-1806: -- Summary: Overlapping dynamic realms don't get updated Key: SYNCOPE-1806 URL: https://issues.apache.org/jira/browse/SYNCOPE-1806 Project: Syncope Issue Type: Bug Components: core Affects Versions: 3.0.6, 2.1.14 Reporter: federico brignola Attachments: docker-compose.yml When two or more dynamic realms have overlapping conditions, Users, Groups and AnyObjects are not added to all the matching realms but only to the first one. Steps to reproduce: # run the following docker-compose environment # create a user "user1" with email "us...@example.com" # create a dynamic realm "dynr1" with condition "USER Dynamic Condition [ATTRIBUTE email NOT NULL]" # create another dynamic realm "dynr2" with the same condition of "dynr1" # // Check that both dynamic realms contain the user "user1" # create a new user "user2" with email "us...@example.com" # // Check that only the realm "dynr1" contains the user "user2" while the other doesn't -- This message was sent by Atlassian Jira (v8.20.10#820010)
