Story #2778
include session subject in NotAuthorized error message
Status:
Closed
Priority:
Low
Assignee:
Ben Leinfelder
Category:
Metacat
Target version:
-
Start date:
Due date:
% Done:
100%
Story Points:
Sprint:
Description
Connections with certain types of bad certificates succeed, but get downgraded to 'public'. It would be helpful for the client to have the subject of the session received by D1Nodeservice.isAuthorized() in the error message returned, as a possible explanation for why the call didn't succeed.
Similarly, it might be helpful when trying to resolve escalated authorization issues if the session subject was logged as a warning when NotAuthorized is triggered. Might be triggered a lot, though, as isAuthorized is called by other api methods.
History
#1 Updated by Dave Vieglais over 12 years ago
- Position changed from 1 to 448
- Target version changed from Sprint-2012.19-Block.3.2 to Sprint-2012.21-Block.3.3
- Position set to 1
#2 Updated by Dave Vieglais over 12 years ago
- Milestone changed from CCI-1.0.0 to CCI-1.1
- Target version deleted (
Sprint-2012.21-Block.3.3)
#3 Updated by Ben Leinfelder about 12 years ago
- Status changed from New to Closed
- translation missing: en.field_remaining_hours set to 0.0
- Start date deleted (
2012-05-17)
Will now include all tested subjects in the error message that is returned. The DNs are delimited by semicolons
