[
https://issues.apache.org/jira/browse/FC-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244103#comment-14244103
]
Shawn McKinney commented on FC-29:
----------------------------------
How do we perform the same operation using apache ldap api?
Here is compare operation
CompareRequest compareRequest = new CompareRequestImpl();
compareRequest.setName( new Dn( dn ) );
compareRequest.setAttributeId( attribute.getId() );
compareRequest.setAssertionValue( attribute.getString() );
// TODO: AUDIT OPENLDAP PROXY CONTROL RIGHT HERE:
String OPENLDAP_PROXY_CONTROL = "2.16.840.1.113730.3.4.18";
org.apache.directory.api.ldap.model.message.ExtendedResponse
extendedResponse = connection.extended( OPENLDAP_PROXY_CONTROL, ( GlobalIds.DN
+ ": " + userDn ).getBytes(
GlobalIds.UTF8 ) );
CompareResponse response = connection.compare( compareRequest );
return response.getLdapResult().getResultCode() ==
ResultCodeEnum.SUCCESS;
> AuditMgr.getUserAuthZ cannot pull back failedOnly
> -------------------------------------------------
>
> Key: FC-29
> URL: https://issues.apache.org/jira/browse/FC-29
> Project: FORTRESS
> Issue Type: Bug
> Affects Versions: 1.0.0-RC39
> Reporter: Emmanuel Lecharny
> 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)
