[
https://issues.apache.org/jira/browse/SYNCOPE-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18091997#comment-18091997
]
ASF subversion and git services commented on SYNCOPE-1978:
----------------------------------------------------------
Commit 3da46df08632bef43b752c8c8d5e4207efca169c in syncope's branch
refs/heads/4_0_X from Oleg Zimakov
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=3da46df086 ]
[SYNCOPE-1978] Search audit events by username (#1443)
> 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
> Assignee: Francesco Chicchiriccò
> Priority: Major
> Fix For: 4.0.7, 4.1.2, 5.0.0
>
> Time Spent: 50m
> 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)
