Re: [higgins-dev] Digital Identity and IContext open() method

[Greg Byrd <gbyrd@xxxxxxxx>]

It's not that we want users to create/use identities in the Higgins 
Framework.  It's more that
we want to allow other standard representations -- those typically used 
to perform authentication
and authorization -- to be passed in.  An example would be an X.509 
certificate or a SAML token
with username and password.

(Perhaps "authToken" would be a better name for the parameter.)

...Greg



Scott Lewis wrote:
> Hi Greg,
>
> > ut I figured that a user would retrieve the policy of a Context,
> > which would tell what sort of credentials are required for opening, 
> > and the
> > format(s) that it requires for passing in those credentials.  It's 
> > then the user's
> > responsibility to get/create such a token.
> >
> > If we provide an interface that represents identity, then we have to 
> > have
> > methods to create that identity, which I think is out of scope.
>
> In ECF we've already done this (created an interface to represent 
> identity...called org.eclipse.ecf.identity.ID).  So ID construction 
> happens (e.g.) via a flexible IDFactory
>
> ID newID = 
> IDFactory.getDefault().createID(namespace,"slewis@xxxxxxxxxxxxx");
>
> Further there is an extension point already defined that allows 
> extensions to define their own Namespaces (e.g. 
> 'myprotocol:urn:blah:de:blah:de:blah').  And to set themselves up as 
> the implementation of the above call (via 'namespace' parameter).
>
> So although out of Higgins scope it would be a useful point of 
> cross-project coordination.
>
> Scott
>
>
> > Tom Doman wrote:
> > > I assumed that the users of Higgins Context Providers wouldn't want to
> > > have to know details about a particular identity class based on which
> > > Context Provider or Providers they choose to use.  Is this not a
> > > concern?
> > >
> > > Tom
> > >
> > >  
> > > > > > Greg Byrd <gbyrd@xxxxxxxx> 7/27/2006 5:20 PM >>>
> > > > > >         
> > >
> > > The provider can require a particular class to be passed in, and can 
> > > test whether
> > > the object is of that type.  Or it could accept one of several classes.
> > >  
> > > This way we
> > > can use "standard" classes without creating a new one just to extend 
> > > something
> > > like IDigitalIdentity.
> > >
> > > ...Greg
> > >
> > >
> > >
> > > Tom Doman wrote:
> > >  
> > > > Jim and I were just having a discussion on the higgins IRC about the
> > > > open method.  Currently, it takes a java.lang.Object.  Why isn't
> > > >     
> > > there
> > >  
> > > > an interface defined for Digital Identity?  I assume we're not gonna
> > > > make the Context Provider implementors guess at what
> > > >     
> > > java.lang.Object
> > >  
> > > > might get passed to represent the identity.  Jim seemed to remember
> > > >     
> > > this
> > >  
> > > > a temporary punt.  Anyone have an thoughts on where we should take
> > > > this?
> > > >
> > > > Thanks,
> > > > Tom
> > > >
> > > > _______________________________________________
> > > > higgins-dev mailing list
> > > > higgins-dev@xxxxxxxxxxx 
> > > > https://dev.eclipse.org/mailman/listinfo/higgins-dev       
> > >
> > > _______________________________________________
> > > higgins-dev mailing list
> > > higgins-dev@xxxxxxxxxxx 
> > > https://dev.eclipse.org/mailman/listinfo/higgins-dev
> > > _______________________________________________
> > > higgins-dev mailing list
> > > higgins-dev@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/higgins-dev
> > >   
> >
> > _______________________________________________
> > higgins-dev mailing list
> > higgins-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/higgins-dev
>
>
> _______________________________________________
> higgins-dev mailing list
> higgins-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/higgins-dev