[
https://issues.apache.org/jira/browse/SHINDIG-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615668#action_12615668
]
Chris Chabot commented on SHINDIG-463:
--------------------------------------
Really ? When people have to write their service classes, is it easier to
explain to them (and have them remember) isAnonymous() or that they should
check some variable and see if it's null?
Also is it easier to understand an exception that says "hey silly, you forgot
to check if this is an anonymous token" or a "*cloud of smoke and debugging
output* you referenced a null variable".
I can't really comment on the java interfaces, but on the PHP side the choice
was easy to make :)
> Support Anonymous Security Tokens
> ---------------------------------
>
> Key: SHINDIG-463
> URL: https://issues.apache.org/jira/browse/SHINDIG-463
> Project: Shindig
> Issue Type: Improvement
> Components: Common Components (Java)
> Reporter: Paul Lindner
> Assignee: Paul Lindner
> Attachments: anontoken.patch
>
>
> To support anonymous access for viewer/owner we need to support the concept
> of an anonymous security token.
> To do this we should create an isAnonymous() method in the SecurityToken
> interface and add a new implementation AnonymousSecurityToken.
> These tokens will throw InvalidArgumentException() when an attempt is made to
> access any field.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
