diff options
| author | slaws <slaws@13f79535-47bb-0310-9956-ffa450edef68> | 2008-09-15 08:07:58 +0000 |
|---|---|---|
| committer | slaws <slaws@13f79535-47bb-0310-9956-ffa450edef68> | 2008-09-15 08:07:58 +0000 |
| commit | fa51018b6c24f598ae8174afa183b0b46436e69b (patch) | |
| tree | b6c37b85d26f0755ba95200227ea942bd2135c00 /java/sca/itest/pom.xml | |
| parent | 5c5b60f1525a5865a3c2bc35263224c2cd79c713 (diff) | |
More work exploring the policy extension model by implementing a token based 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
Diffstat (limited to '')
| -rw-r--r-- | java/sca/itest/pom.xml | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/java/sca/itest/pom.xml b/java/sca/itest/pom.xml index b2af34b305..1c32e2489c 100644 --- a/java/sca/itest/pom.xml +++ b/java/sca/itest/pom.xml @@ -106,6 +106,7 @@ <module>policy-security</module> <module>policy-security-basicauth</module> <module>policy-security-jsr250</module> + <module>policy-security-token</module> <module>properties</module> <module>recursive</module> <module>recursive-multi-level</module> |