[
https://issues.apache.org/jira/browse/SYNCOPE-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18091742#comment-18091742
]
Oleg Zimakov edited comment on SYNCOPE-1978 at 6/26/26 4:32 AM:
----------------------------------------------------------------
I suggest us using a dedicated search parameter `username` instead of reusing
`entityKey` since it's going to be fuzzy semantics (it can be GUID or it can be
string literal). Besides, we can make `username` repeatable, so we can provide
a list of users we're interested in.
was (Author: JIRAUSER313063):
I suggest us using a dedicated search parameter `username` instead of reusing
`entityKey` since it's going to be fuzzy semantics (it can be GUID or it can be
string literal).
> Search in auditevent based on username
> --------------------------------------
>
> Key: SYNCOPE-1978
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1978
> Project: Syncope
> Issue Type: Improvement
> Components: core
> Affects Versions: 4.0.6
> Reporter: Lionel Schwarz
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In Syncope 3.0, it was possible to search audit entries by username [1].
> Looking at the code [2], I guess it was actually a bug.
> In syncope 4.0, this seems to be fixed [3]and therefore it is not possible to
> do this.
> This functionnality would be very useful when it is not possible to get the
> real key of a user (for example after deletion)
>
>
> [1] GET /audit/entries?entityKey=LOGIN
> [2]
> [https://github.com/apache/syncope/blob/syncope-3.0.16/core/persistence-jpa/src/main/java/org/apache/syncope/core/persistence/jpa/dao/JPAAuditConfDAO.java#L58]
> [3]
> [https://github.com/apache/syncope/blob/syncope-4.0.6/core/persistence-jpa/src/main/java/org/apache/syncope/core/persistence/jpa/dao/JPAAuditEventDAO.java#L51]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
