| Scenario IdAS Endpoint Use Cases - Given an IdAS
endpoint, and the "user" as the consumer of the IdAS API supported by the
endpoint...
IdASE1 - User has URI of a Context and wishes to open it. There are no
constraints on the provider.
IdASE2 - User has URI of a Context and wishes to open it using a specific
provider.
IdASE3 - User wishes to determine which providers are available for a
particular Context (URI).
IdASE4 - User wishes to import a Context whose data is represented in a
specific format (e.g., LDAP).
IdASE5 - User wishes to find out which Contexts are available using the
currently-installed providers.
IdAS Registry Use Cases
IdASR1 - User wants to create/open a "private" Context, for which he
has a URI.
(1) Gets a list of potential factories for this Context
(IdASRegistry.getContextFactories(URI)).
(2) Chooses one and creates a Context object (factory.createContext)
then opens it (context.open).
(3) If another user of the service calls IdASRegistry.getContexts, this
URI does not appear in the list.
IdASR2 - User wants to publish a Context, for which he has a URI.
(1) Calls IdASRegistry.registerContext(URI) -- registry will test the
URI against the existing factories (factory.canCreate), and will throw
an exception if there is no factory that claims to handle this URI.
(Note that the user does not need to create or open this ContextRef to
register it.)
(2) If another user of the service calls IdASRegistry.getContexts, this
URI will appear in the list.
I
|