summaryrefslogtreecommitdiffstats
path: root/sca-java-2.x/tags/2.0.1-RC1/modules/policy-security/src/main/java/org/apache/tuscany/sca/policy/authentication/basic/BasicAuthenticationPrincipal.java (unfollow)
Commit message (Collapse)AuthorFilesLines
2013-10-07Official Tuscany 2.0.1 Releaselresende1-80/+0
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1530096 13f79535-47bb-0310-9956-ffa450edef68
2013-09-302.0.1 RC1 release taglresende1-0/+0
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1527464 13f79535-47bb-0310-9956-ffa450edef68
2009-03-17[maven-release-plugin] copy for branch fooantelder1-0/+0
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@755220 13f79535-47bb-0310-9956-ffa450edef68
2008-12-02Branch for 1.4ramkumar1-0/+0
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@722428 13f79535-47bb-0310-9956-ffa450edef68
2008-11-13Creating Java SCA 1.x branchlresende1-0/+0
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@713805 13f79535-47bb-0310-9956-ffa450edef68
2008-09-15More work exploring the policy extension model by implementing a token based ↵slaws1-0/+80
authentication schema across binding.ws and binding.jm. No authentication is actually performed here. That is left for users to provide their own policy interceptors. However tokens are passed and security Subjects/Principals are created. This exercise has highlighted some awkwardness in the process of building policy implementations. I'll post about this on the mail list. git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@695374 13f79535-47bb-0310-9956-ffa450edef68