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"
(→Service) |
|||
| Line 51: | Line 51: | ||
The above messages can also be combined 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 Type]]s will be returned, AND an Attribute Service endpoint will be instantiated. | The above messages can also be combined 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 Type]]s will be returned, AND an Attribute Service endpoint will be instantiated. | ||
| − | == Entities == | + | === Entities === |
A client can request an [[Entity UDI]] to be resolved: | A client can request an [[Entity UDI]] to be resolved: | ||
| Line 65: | Line 65: | ||
$value | $value | ||
"[Entity UDI]" | "[Entity UDI]" | ||
| + | $authn$type | ||
| + | [Authentication Materials Type] | ||
| + | $authn | ||
| + | "[Authentication Materials]" | ||
</source> | </source> | ||
| − | == Attributes == | + | === Attributes === |
A client can request an [[Attribute UDI]] to be resolved: | A client can request an [[Attribute UDI]] to be resolved: | ||
| Line 82: | Line 86: | ||
$value | $value | ||
"[Attribute UDI]" | "[Attribute UDI]" | ||
| + | $authn$type | ||
| + | [Authentication Materials Type] | ||
| + | $authn | ||
| + | "[Authentication Materials]" | ||
</source> | </source> | ||
Revision as of 15:11, 13 July 2009
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
-- WORK IN PROGRESS --
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.
Javadoc
- Javadoc: Javadoc
Service
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.
$ $get / $ $uri$http <-- request an Attribute Service endpoint for the Context --> $ $value "[Context UDI]" $authn$type [Authentication Materials Type] $authn "[Authentication Materials]"
The above messages can also be combined 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:
$ $get / = $uri$http <-- request an Attribute Service endpoint for the Context --> = <-- request the Entity ID --> = $value "[Entity UDI]" $authn$type [Authentication Materials Type] $authn "[Authentication Materials]"
Attributes
A client can request an Attribute UDI to be resolved:
$ $get / + $uri$http <-- request an Attribute Service endpoint for the Context --> = <-- request the Entity ID --> + <-- request the Attribute ID --> + $value "[Attribute UDI]" $authn$type [Authentication Materials Type] $authn "[Authentication Materials]"
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