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.
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.
Shash
Michael Nash JGlobal.com wrote:
Shash:
I just tripped over an excellent example of why this needs to be done: I have a need for a Keel app that has no database, e.g. doesn't use the persistence service at all. Currently, that's not possible - I wrote a svc-authentication-config and a svc-authorization-config, but the current authentication is the default and a bit hard-wired. We'd need to break out svc-authentication-persist in order to allow this type of app.
Any problem if I make a start on this by breaking out svc-authentication-persist first, and leave the rest for you over the weekend?
Mike
http://keelframework.org/documentation Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
