[
https://issues.apache.org/jira/browse/SHINDIG-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645275#action_12645275
]
Kevin Brown commented on SHINDIG-675:
-------------------------------------
That's intentional. There are an infinite number of ways to expose the
authentication mechanism.
It seems more likely that we need a generic way of extending the SecurityToken.
I still believe strongly in a method like:
String getProperty(String name)
on the SecurityToken interface. These issues keep coming up and the solutions
proposed for dealing with it range from annoying to incomprehensible. Why not
just add a property bag?
> Security token does not expose the authentication mechanism used to generate
> it
> -------------------------------------------------------------------------------
>
> Key: SHINDIG-675
> URL: https://issues.apache.org/jira/browse/SHINDIG-675
> Project: Shindig
> Issue Type: Improvement
> Components: RESTful API (Java)
> Reporter: Louis Ryan
> Assignee: Louis Ryan
>
> The security token interface does not expose the method of authentication
> used to generate it. Containers will likely have ACL policies that vary by
> the authentication mode.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
