Agreed. I saw your comments on the lift mailing list. Looks like it is a good start but I didn't see any details on container-based auth.
D. -----Ursprüngliche Nachricht----- Von: Darren Hague [mailto:[email protected]] Gesendet: Fr 1/2/2009 13:26 An: [email protected] Cc: [email protected]; Bill Fernandez Betreff: Re: AW: AW: Thoughts on building a business around ESME Agreed. Top of my list right now is replacing/augmenting the OpenID authentication with J2EE-based authentication (which would then allow easy integration of directory servers, etc.), as a first step towards implementing further authorisation options. - Darren Hirsch, Richard wrote: >> Along with this, of course, we need to implement the >> personal/group/local/global permissions model. >> > > If you look at Mike's blog, you will see that he also thinks this sort of > access control is critical. I agree and I think it should be on the top of > our feature list. > > D. > > > -----Ursprüngliche Nachricht----- > Von: Darren Hague [mailto:[email protected]] > Gesendet: Fr 1/2/2009 12:50 > An: [email protected] > Cc: [email protected]; Bill Fernandez > Betreff: Re: AW: Thoughts on building a business around ESME > > I think that a useful lever for ESME adoption would be to make sure that > Twitter (& Yammer?) integration is built-in - in other words, ESME > should be usable as a Twitter client, so people can access their wider > network. Once this is under way, integrating local users becomes easier. > > A useful default would be for users to specify their Twitter ID on > registration/first login, and this would be their ESME ID too - @xyz > would then work seamlessly. We would then need a convention for > specifiying local-only users (i.e. those who do not have a Twitter > account) - perhaps @_abcd or something similar. > > Along with this, of course, we need to implement the > personal/group/local/global permissions model. > > - Darren > > >
