There is also the issue of tracking individual message flags per user. For instance, if a mailbox has two users, each user must be able to flag a message as read without affecting the other user's flags.
The current (not yet commited) mailbox implementation provides a list of subscribed users per mailbox. Each user has a seperate pseudo-mailbox. Since mailboxes do not store actual messages, but only a reference to a message in the message store, the overhead is not significant. JAAS provides a domain-wide role mapping, with no way to specify what object the role applies to. What we need is a role per folder. One way to get around this problem is to impose a naming convention, something like <object name>.<role name>, but this may be difficult to configure if the installation uses an external system to manage users and roles. Perhaps a solution would be to develop a custom login module that can manage the roles for jbmail, using another (optional) login module to provide authentication, or else a completely seperate access rights module, using JAAS for authentication and system-level security. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862290#3862290 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862290 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
