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 "Org.eclipse.higgins.idas.proxy"
(2 intermediate revisions by the same user not shown) | |||
Line 2: | Line 2: | ||
[[Image:Higgins_logo_76Wx100H.jpg|right]] | [[Image:Higgins_logo_76Wx100H.jpg|right]] | ||
− | This page describes the '''higgins.idas.proxy''' component (IdAS Proxy) which exposes [[IdAS]] services at an XDI endpoint. The idea is that the IdAS Proxy runs a full IdAS stack including a set of [[Context Provider]]s. Thin clients can then talk to this IdAS Proxy. | + | This page describes the '''higgins.idas.proxy''' component (IdAS Proxy), which exposes [[IdAS]] services at an XDI endpoint. The idea is that the IdAS Proxy runs a full IdAS stack including a set of [[Context Provider]]s. Thin clients can then talk to this IdAS Proxy. |
The IdAS Proxy uses the [[Org.eclipse.higgins.idas.udi|UDI Resolver]] for resolving UDIs on a client's behalf. | The IdAS Proxy uses the [[Org.eclipse.higgins.idas.udi|UDI Resolver]] for resolving UDIs on a client's behalf. | ||
The IdAS Proxy uses the [[Attribute Service]] for exposing a [[Context]] after opening it on a client's behalf. | The IdAS Proxy uses the [[Attribute Service]] for exposing a [[Context]] after opening it on a client's behalf. | ||
+ | |||
+ | If configured appropriately, the IdAS Proxy can act as a [[Personal Data Store]]. | ||
==Javadoc== | ==Javadoc== | ||
Line 35: | Line 37: | ||
<source lang="java"> | <source lang="java"> | ||
− | + | =sender | |
$get | $get | ||
/ | / | ||
$ | $ | ||
$uri$http <-- request an Attribute Service endpoint for the Context --> | $uri$http <-- request an Attribute Service endpoint for the Context --> | ||
+ | $ | ||
$value | $value | ||
"[Context UDI]" | "[Context UDI]" | ||
Line 55: | Line 58: | ||
<source lang="java"> | <source lang="java"> | ||
− | + | =sender | |
$get | $get | ||
/ | / | ||
Line 75: | Line 78: | ||
<source lang="java"> | <source lang="java"> | ||
− | + | =sender | |
$get | $get | ||
/ | / |
Latest revision as of 04:16, 9 January 2010
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
This page describes the higgins.idas.proxy component (IdAS Proxy), which exposes IdAS services at an XDI endpoint. The idea is that the IdAS Proxy runs a full IdAS stack including a set of Context Providers. Thin clients can then talk to this IdAS Proxy.
The IdAS Proxy uses the UDI Resolver for resolving UDIs on a client's behalf.
The IdAS Proxy uses the Attribute Service for exposing a Context after opening it on a client's behalf.
If configured appropriately, the IdAS Proxy can act as a Personal Data Store.
Javadoc
- Javadoc: Javadoc
Service
XDI Messages are used by a client to communicate both with the IdAS Proxy and the Attribute Service. The following sections describe the XDI messages understood by the IdAS Proxy.
Contexts
A client can request a Context UDI to be resolved to Context Metadata:
=sender $get / $ $is$a <-- request the Context Types --> $authn$type <-- request the Authentication Materials Types --> $authn <-- request the Authentication Materials --> $ $value "[Context UDI]"
A client can request a Context UDI to be resolved and an Attribute Service endpoint to be instantiated for the Context.
=sender $get / $ $uri$http <-- request an Attribute Service endpoint for the Context --> $ $value "[Context UDI]" $authn$type [Authentication Materials Type] <-- type of Authentication Materials for opening the Context --> $authn "[Authentication Materials]" <-- Authentication Materials for opening the Context -->
The above messages can also be combined in different ways by including all desired XDI predicates in the XDI request. For example, if the predicate $is$a and $uri$http are included in the message, the Context Types will be returned, AND an Attribute Service endpoint will be instantiated.
Entities
A client can request an Entity UDI to be resolved:
=sender $get / = $uri$http <-- request an Attribute Service endpoint for the Context --> = <-- request the Entity ID in the Context --> = $value "[Entity UDI]" $authn$type [Authentication Materials Type] <-- type of Authentication Materials for opening the Context --> $authn "[Authentication Materials]" <-- Authentication Materials for opening the Context -->
Attributes
A client can request an Attribute UDI to be resolved:
=sender $get / + $uri$http <-- request an Attribute Service endpoint for the Context --> = <-- request the Entity ID in the Context --> + <-- request the Attribute ID on the Attribute --> + $value "[Attribute UDI]" $authn$type [Authentication Materials Type] <-- type of Authentication Materials for opening the Context --> $authn "[Authentication Materials]" <-- Authentication Materials for opening the Context -->
See Also
- [[1]] - Universal Data Identifiers
- Identity Attribute Service --overview of IdAS
- Components: IdAS Component --lists IdAS Component sub-projects and as well as projects for available Context Providers