Bug #2516
cn.getLogRecords() errors vs. cn-dev
100%
Description
when calling cn.getLogRecords() with session subject set, am getting a ServiceFailure. But the http status code is 200, so the client attempts to deserialize the error xml to the Log datatype. should be 500.
Secondly, the ServiceFailure indicates another problem with the implementation. I believe that the subject lookup is to get a trusted subjectInfo, and think the desired behavior is to allow the subjectInfo to be empty, and proceed without groups and equivalent identities and verified statuses.
the returned content from the call:
<?xml version="1.0" encoding="UTF-8"?>
Problem looking up entry: CN=testRightsHolder,DC=dataone,DC=org : [LDAP: error code 32 - No Such Object]
Subtasks
History
#1 Updated by Rob Nahf over 12 years ago
- Category changed from d1_log_aggregation to d1_cn_solr_extensions
- Assignee changed from Skye Roseboom to Robert Waltz
#2 Updated by Rob Nahf over 12 years ago
- Status changed from New to In Progress
- Assignee changed from Robert Waltz to Rob Nahf
d1_identity_manager
CNIdentityLDAPImpl.getSubjectInfo() doesn't throw NotFound or NotAuthorized exceptions, but simply ServiceFailure. Need to add that exception to throws clause. Will impact other dependent services.
d1_solr_extensions
SessionAuthorizationFilter.doFilter() also doesn't handle the "not found" situation, but instead sends along the ServiceFailure.
#3 Updated by Rob Nahf over 12 years ago
- Status changed from In Progress to Closed
