You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Shawn McKinney (JIRA)" <ji...@apache.org> on 2015/04/27 18:20:38 UTC

[jira] [Issue Comment Deleted] (FC-33) AuditMgr.getUserAuthZ cannot pull back faileOnly

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

Shawn McKinney updated FC-33:
-----------------------------
    Comment: was deleted

(was: and Kiran has recommended using env variables:

use FORTRESS_HOME or FORTRESS_CONF env variable and read the config from that location. If this variable is not set then the default config can be extracted and used.
)

> AuditMgr.getUserAuthZ cannot pull back faileOnly
> ------------------------------------------------
>
>                 Key: FC-33
>                 URL: https://issues.apache.org/jira/browse/FC-33
>             Project: FORTRESS
>          Issue Type: Bug
>    Affects Versions: 1.0.0-RC39
>            Reporter: Shawn McKinney
>             Fix For: 1.0.0
>
>
> This search filter:
> filter += "(" + REQASSERTION + "=" + GlobalIds.AUTH_Z_FAILED_VALUE + ")";
> in AuditDAO.getAllAuthZs does not work.  It appears the reqAssertion attribute cannot be searched on within the auditCompare object class.  Have tested with ldapbrowser and does not pull back entries.  Will need to come up with a work around.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)