Shash: > This may be too late since you already implelmented > svc-authentication-config, but FYI, the Tagish library also has an > example JAAS-based login module to get auth. data from flat-files.
Ah - didn't know that. Besides, I was looking for something that used the standard *-system.xconf method in any case. > Also, regarding the default authentication. I think this is one are we > should look into after 2.0. Currently every model and service, that > uses *other* services, uses hard-coded hints (mostly, "default" or > "*"). I think we should change all our services like this to implement > Configurable and optionally provide hint names for each service used. > The default can still be kept as "default" or "*" or the current value > for backward-compatibility. But, this would allow us to fully utilize > the potential of switching of components in COP. I'm not sure I follow - are you saying we should break out default auth *after* 2.0, and then implement the hint idea, or break out auth before 2.0, then after 2.0 deal with the hints? Just FYI, I've got auth mostly broken out now... Michael Nash JGlobal Ltd. http://www.jglobal.com Bahamas Commerce and Trade http://www.bahamascommerce.com http://keelframework.org/documentation Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
