You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@syncope.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2023/02/04 10:39:00 UTC

[jira] [Commented] (SYNCOPE-1727) Elasticsearch cannot find anything under given Realm in case of parent update

    [ https://issues.apache.org/jira/browse/SYNCOPE-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17684139#comment-17684139 ] 

ASF subversion and git services commented on SYNCOPE-1727:
----------------------------------------------------------

Commit 624487e9cb3cdcc8f6bcf8a4436641bef3708ab5 in syncope's branch refs/heads/3_0_X from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=624487e9cb ]

[SYNCOPE-1727] Indexing realm values by key, not by full path (#407)



> Elasticsearch cannot find anything under given Realm in case of parent update
> -----------------------------------------------------------------------------
>
>                 Key: SYNCOPE-1727
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1727
>             Project: Syncope
>          Issue Type: Bug
>          Components: extensions
>    Affects Versions: 2.1.13, 3.0.1
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>            Priority: Major
>              Labels: elasticsearch
>             Fix For: 3.0.2, 4.0.0
>
>
> Even though not allowed from Console, REST services consent to change parent of any Realm. e.g. to move Realms around the tree.
> In such cases, Elasticearch is not able to find any more Users, Groups or Any Objects under the moved Realm. The reason is that the current index is build out of Realm fullpath, which will naturally change after move.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)