Issue Details (XML | Word | Printable)

Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Sivakumar Thyagarajan
Reporter: Sivakumar Thyagarajan
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.

Incorrect non-null constraint for serviceSubject in SecurityContext.setupSecurityContext's javadoc

Created: 07/Mar/13 04:31 PM   Updated: 28/Mar/13 05:32 AM   Resolved: 28/Mar/13 05:32 AM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Tags: javadoc connector 1_6 security inflow
Participants: Sivakumar Thyagarajan

 Description  « Hide

The Connector 1.6 (and the current 1.7) javadoc for SecurityContext ( ) has the following erroneous non-null constraint for serviceSubject.

In the description of setupSecurityContext [1], we have the following erroneous line:
"The serviceSubject argument must be non-null and it must not be read-only."

In the spec, and in the same method's 'serviceSubject' parameter javadoc, we talk about serviceSubject being nullable. The correct statement must be
"The serviceSubject argument may be null, and when not null it must not be read-only."


Sivakumar Thyagarajan added a comment - 28/Mar/13 05:32 AM

Fixed in the final version of the Connector 1.7 spec.