[
http://java.net/jira/browse/JASPIC_SPEC-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
JeffTancill moved GLASSFISH-19348 to JASPIC_SPEC-12:
----------------------------------------------------
Project: jaspic-spec (was: glassfish)
Key: JASPIC_SPEC-12 (was: GLASSFISH-19348)
Assignee: (was: JeffTancill)
Component/s: (was: security)
Fix Version/s: (was: 4.0)
> Leverage SAML Web SSO from Nobis in JASPIC TCK
> ----------------------------------------------
>
> Key: JASPIC_SPEC-12
> URL: http://java.net/jira/browse/JASPIC_SPEC-12
> Project: jaspic-spec
> Issue Type: New Feature
> Reporter: JeffTancill
> Original Estimate: 2 weeks
> Remaining Estimate: 2 weeks
>
> The Nobis project is the RI for JSR-351. It also contains the SAML Web SSO implementation that will be leveraged within the JASPIC TCK in order to do two things:
> 1) Ensure that an actual and useful SAM can be configured for use within an application server implementation using standard mechanisms. To date the TCK has only tested spec compliance with a special set of implementation classes that ensure that the correct APIs are being called at the correct times
>
> 2) Ensure that Java EE 6+ environments are capable of participating in three party authentication exchanges and enterprise SSO products
> the current implementation encompasses the resource first usecase wherein the resource is requested first and the user is redirected to the configured IDP for authentication
> The TCK will need to acquire the appropriate implementation from Nobis, make it available in the system classpath for the appserver being tested
> and configure it for use within the system and for a particular application.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://java.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira