https://bugzilla.redhat.com/show_bug.cgi?id=768934 El día 14 de diciembre de 2011 22:13, Rich Megginson <rmeggins@xxxxxxxxxx> escribió: > On 12/12/2011 06:53 AM, Juan Asensio Sánchez wrote: >> >> Hi >> >> I am trying to test the proxied operations in 389 DS. For now, I have >> written a small script using UnboundID LDAP SDK [1]: >> >> ModifyRequest modifyRequest = new >> ModifyRequest("uid=XXXXXXXX,ou=People,o=XXXXXXXX,dc=XXXXXXXX,dc=XXXXXXXX", >> new Modification(ModificationType.REPLACE, "address", "Nueva >> dirección")); >> modifyRequest.addControl(new ProxiedAuthorizationV2RequestControl( >> "dn:" + proxiedUserEntry.getDN()) ); >> >> try >> { >> LDAPResult modifyResult = >> ldapConnectable.getConnection(session).modify(modifyRequest); >> // If we got here, then the modify was successful. >> } >> catch (LDAPException le) >> { >> System.out.println(le.getDiagnosticMessage() + " (" + >> le.getResultCode() + ")"); >> } >> >> Although I have not yet assigned any ACIS as described in [2], I >> supposed to get a denied response, not a protocol error as I get: >> >> unable to parse proxied authorization control (2 (protocol error)) >> >> I think this error is returned by the LDAP server, although it is not >> reported in the error LOG. Anyone has experienced with proxied >> operations? > > Please file a bug at https://bugzilla.redhat.com/enter_bug.cgi?product=389 >> >> >> [1] http://www.unboundid.com/products/ldapsdk/docs/javadoc/index.html >> [2] >> http://docs.redhat.com/docs/en-US/Red_Hat_Directory_Server/8.2/html/Administration_Guide/Managing_Access_Control-Access_Control_Usage_Examples.html#Access_Control_Usage_Examples-Proxied_Authorization_ACI_Example >> -- >> 389 users mailing list >> 389-users@xxxxxxxxxxxxxxxxxxxxxxx >> https://admin.fedoraproject.org/mailman/listinfo/389-users > > -- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
