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

Posted to dev@ranger.apache.org by "Andrew Luo (Jira)" <ji...@apache.org> on 2023/02/21 12:38:00 UTC

[jira] [Updated] (RANGER-4104) XXAuthSessionDao.getRecentAuthFailureCountByLoginId produces incorrect SQL code

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

Andrew Luo updated RANGER-4104:
-------------------------------
    Attachment: 0001-Fix-type-of-authWindowStartTime-parameter-in-XXAuthS.patch

> XXAuthSessionDao.getRecentAuthFailureCountByLoginId produces incorrect SQL code
> -------------------------------------------------------------------------------
>
>                 Key: RANGER-4104
>                 URL: https://issues.apache.org/jira/browse/RANGER-4104
>             Project: Ranger
>          Issue Type: Bug
>          Components: admin
>    Affects Versions: 3.0.0, 2.4.0
>            Reporter: Andrew Luo
>            Priority: Major
>         Attachments: 0001-Fix-type-of-authWindowStartTime-parameter-in-XXAuthS.patch
>
>
> XXAuthSessionDao.getRecentAuthFailureCountByLoginId produces incorrect SQL code due to an error in how the authWindowStartTime Date parameter is bound.
> It is currently bound with setParameter("authWindowStartTime", authWindowStartTime) however, [JPA 2.2 Specification Section 11.1.53|https://download.oracle.com/otn-pub/jcp/persistence-2_2-mrel-spec/JavaPersistence.pdf] says that it should be bound by specifying an additional parameter TemporalType.DATE.



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