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

Posted to dev@syncope.apache.org by "Francesco Chicchiriccò (Jira)" <ji...@apache.org> on 2023/11/18 07:23:00 UTC

[jira] [Resolved] (SYNCOPE-1790) Swagger filtered GET returns multiple Users/AnyObjects instead of one

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

Francesco Chicchiriccò resolved SYNCOPE-1790.
---------------------------------------------
    Resolution: Fixed

> Swagger filtered GET returns multiple Users/AnyObjects instead of one
> ---------------------------------------------------------------------
>
>                 Key: SYNCOPE-1790
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1790
>             Project: Syncope
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.0.5
>            Reporter: Daniele Cipollone
>            Assignee: Francesco Chicchiriccò
>            Priority: Major
>             Fix For: 3.0.6, 4.0.0
>
>
> The bug has been reproduced locally with a Syncope 3.0.5 clean archetype using PGJSONB .
> Basically, if there are 2 users with one email address that contains the other, the GET on Swagger filtered with the fiql expression returns both users. In particular:
> 2 users have been created created on Syncope:
> The value "utente.uno@email.it" has been assigned to user1 email
> The value "dueutente.uno@email.it" has been assigned to user2 email
> Then, the GET /users has been executed on Swagger with the fiql expression "email==utente.uno@email.it" and it returned both users.
> On the actual project instead, the problem was found in the same way, but with the attribute email of an AnyObject, with the GET /anyObjects, filtered with AnyObject type and email value



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