syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francesco Chicchiriccò (Jira) <j...@apache.org>
Subject [jira] [Assigned] (SYNCOPE-1480) Elasticsearch:dynrealm assignment not updated on condition change
Date Wed, 11 Sep 2019 11:26:00 GMT

     [ https://issues.apache.org/jira/browse/SYNCOPE-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Francesco Chicchiriccò reassigned SYNCOPE-1480:
-----------------------------------------------

    Assignee: Francesco Chicchiriccò

> Elasticsearch:dynrealm assignment not updated on condition change
> -----------------------------------------------------------------
>
>                 Key: SYNCOPE-1480
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1480
>             Project: Syncope
>          Issue Type: Bug
>          Components: core, extensions
>    Affects Versions: 2.0.13, 2.1.4
>            Reporter: Andrea Patricelli
>            Assignee: Francesco Chicchiriccò
>            Priority: Major
>             Fix For: 2.0.14, 2.1.5, 3.0.0
>
>
> # Enable elasticsearch extension and setup ES indexes, etc.
>  # Login as admin to console
>  # Create a dynamic realm with a condition on an USER attribute
>  # Add or change an attribute to an user in order to match that dynamic realm
>  # Check that on ES dynRealms field of the specific user has been populated with the
dynRealm value.
>  # Update dyn realm condition of the dyn realm created at step 3, in order to *not match
anymore* the user at step 4.
>  # Check that on Syncope dynamic realm is no more assigned
>  # On elasticsearch dynRealms field is still populated with the dynamic realm created
at step 3.
> This is due to missing event notification in https://github.com/apache/syncope/blob/syncope-2.0.13/core/persistence-jpa/src/main/java/org/apache/syncope/core/persistence/jpa/dao/JPADynRealmDAO.java#L114-L119



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Mime
View raw message