> From: "Marc Lustig" <[EMAIL PROTECTED]> Mail list archaeologist at large ;-) > > Hi Scott, and everybody, > more than a year ago you wrote the message below. > (There has been no reply to your message.) > What I need to do is building a security framework for customers to inherit > their rights (roles,permissions) to sub-customers. I have app-tables that > hold reseller-specific security data. This is supposed to be kind of > extension of the basic turbine security framework. (I can't explain the > whole thing, it's rather complex.) > Anyway, I need to reference various turbine security tables. > So I wonder if you have figured out a solution for the problem that you > outlined in your message. > I was thinking about aliasing all the tables (like for extending the user) > but I'd like to make sure there isn't any better/easer solution before. > > TIA. > Marc The solution involved using an alias as described in the extend-user-howto document - i.e. the turbine 2.1 solution. It should be achievable under turbine 2.2bx, but it may require the use of the fulcrum security service rather than the one included in turbine itself (and I keep pointing people to Henning's proposed security service even though I haven't yet had the chance to try it myself).
That's about all I can say until I find the time to look into this myself. Sorry I can't be of more help. Cheers, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
