| Re: [higgins-dev] Getting started with IdAS? |
|
Here are some things that might address some of the confusion:
- A CP (Context Provider) can produce any number of IContext instances.
- A CP is just a term meaning a packaging of classes that implement the various IdAS interfaces.
- An IContext instance provides the view of a Context.
- An IContetFactory is implemented by each CP and produces (and could pool, cache, etc.) IContext instances.
- A Context is often backed by an underlying data store (as is the case with the JNDI provider when configured to use LDAP)
So, the relationship between a CP and an underlying connection is really up to the CP. In the case of the JNDI (using LDAP) CP, the JNDIContextFactory will produce any number of IContext instances, each with a 1:1 relationship with an LDAP connection.
Authentication is different. Any IContext instance could have its open/close method called any number of times. Each time, this could cause a new authentication to happen. In the case of the JNDI (using LDAP) CP, open is designed to do an LDAP bind, and close is designed to do an LDAP unbind (I'm not sure if this is the exact behavior today -- it's what's intended though).
Jim
>>> "Marc Boorshtein" <mboorshtein@xxxxxxxxx> 3/9/07 7:55 AM >>> > > Currently, the only component being automatically built (and thus > downloadable) is idas. I know you can get and build idas, the jndi cp, and > the token service. Each component should have build instructions here. > OK, I've got the source for the IdAS and the jndi CP. Thanks. > Yes, IContext.open is effectively authenticate. close is the opposite of > open. I'm not sure why, but the idas javadoc from the nightly build seems > to be broken right now. An alternate (though not in sync with the latest > head code) version is here: > http://www.eclipse.org/higgins/org.eclipse.higgins.docs/idas/ > OK. I'm still a bit confused but I'll go through the IdAS code. The main point of my confusion is the relationship between a CP and an underlying connection. IE the jndi cp only has a single JNDI context. Does this mean that there is a 1-1 relationship between a cp and an authenticated user? Would this in turn indicate multiple instances of a context provider are pooled inside of the IdAS? Thanks again for the help Marc > Jim > > >>> "Marc Boorshtein" <mboorshtein@xxxxxxxxx> 3/8/07 10:51 PM >>> > > > #1 was a topic of discussion a couple days ago on the irc or some form of > IM > > as well. It was suggested that Tom put together instructions on how to > > install/configure the JNDI context provider. I think it will show up here > > soon > > http://wiki.eclipse.org/index.php/JNDI_Context_Provider > > > > Ok, I'll check it out once it's done > > > For #2, there are unit tests for the JNDI CP, but I don't think there's > much > > beyond that (we should probably put out some sample code). If you want to > > do something more complex, you could deploy the Token Service, backed by > the > > JNDI CP which is backed by an LDAP server. > > > > the token service...great.Is that a download yet? I only saw the > idas.jar under downloads > > > At least for #1, to get started you can build IdAS and the JNDI CP > > (instructions here and here) > > > > Ok, I've got these setup. One question (might be unrelated). Is the > "open" method on the context provider supposed to be an authentication > method? It appears to be based on the "sample" in the jndi "dev" > package. > > Thanks > Marc > _______________________________________________ > 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 |