Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Authentication Materials"
(→Goals) |
(→Goals) |
||
| Line 10: | Line 10: | ||
We would like to be able to do the following: | We would like to be able to do the following: | ||
* Have identifiers for common types of Authentication Materials | * Have identifiers for common types of Authentication Materials | ||
| − | ** This is needed in scenarios when you do not know a priori what type(s) of Authentication | + | ** This is needed in scenarios when you do not know a priori what type(s) of Authentication Materials a [[Context]] accepts. |
** For example, for [[R-Card]]s we use [[UDI]]s to point to Higgins [[Context]]s and [[Entity|Entities]]. When a [[UDI]] is resolved, we need to know what type of Authentication Materials is needed for opening the Context it points to. | ** For example, for [[R-Card]]s we use [[UDI]]s to point to Higgins [[Context]]s and [[Entity|Entities]]. When a [[UDI]] is resolved, we need to know what type of Authentication Materials is needed for opening the Context it points to. | ||
* (De-)serialize a concrete instance of Authentication Materials (e.g. to/from XML, String, etc.) | * (De-)serialize a concrete instance of Authentication Materials (e.g. to/from XML, String, etc.) | ||
Revision as of 13:57, 5 March 2009
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
Contents
About
This page describes the concept of Authentication Materials used in the Context Data Model 1.1. Authentication Materials are needed to open a Context.
Current Situation
Currently, IdAS authentication materials in the IContext.open() call are defined to be just a java.lang.Object. This gives maximal flexibility to Context Provider implementations.
Goals
We would like to be able to do the following:
- Have identifiers for common types of Authentication Materials
- This is needed in scenarios when you do not know a priori what type(s) of Authentication Materials a Context accepts.
- For example, for R-Cards we use UDIs to point to Higgins Contexts and Entities. When a UDI is resolved, we need to know what type of Authentication Materials is needed for opening the Context it points to.
- (De-)serialize a concrete instance of Authentication Materials (e.g. to/from XML, String, etc.)
- This is useful in scenarios in which you send Authentication Materials over the network, e.g. in IdAS REST interfaces such as http://code.bandit-project.org/trac/wiki/OTIS and the XDI Engine.
Proposal
The proposal is to do the following:
- Define the following identifiers for common types of Authentication Materials:
- Introduce an interface "IAuthnMaterials" in org.eclipse.higgins.idas.api.
- Make this only a marker interface without methods
- As a convention, implementations of this interface should