Hi all. 

As we look to better manage multiple, technologically-dissimilar applications in order to ease application management tasks, the topic of security has surfaced. Does anyone have thoughts on whether the StrataFrame Role-Based Security (RBS) model and database could be leveraged to become a single user authentication/permissioning system used by departmental web and windows applications, both SF and non-SF based? 

This is very early in the brainstorming phase, but the idea would be that given our usually-similar user roles across multiple applications, we'd setup a StrataFrame security database and use it for all/most apps to determine a given user's role and permissions. As an example assume that one of our users is considered an "admin" and can perform similar "admin-like" duties across a suite of applications. We'd like those apps to all hit against the SF RBS database to determine what permission "keys" the "admin" has. 

Hopefully the above is succinct, yet sufficiently clear enough to make sense. Any thoughts are appreciated. Obviously this is outside the scope of what our friends in Texas had in mind, but...

________________
_____/ Regards,
____/ al

Greg - 

Definitely help. Thanks! Sounds in line with what I was expecting, including the concern over reusing permissions across multiple apps. Last time I worked on RBS (to setup the initial implementation of a StrataFrame Role-Based Security (RBS) enabled app), I did decide to go with a separate security database for the reasons you gave. Also decided that permissions would be app-specific, but named to facilitate security management. So, I'd have things like

Edit - App A

Edit - App B

ReadOnly - App A

ReadOnly - App x

Appreciate the quick reply! 

________________
_____/ Regards,
____/ al

It looks like you are in good shape.  The hard part will likely be getting non-SF apps to work with it, but that's doable...and if they are .NET apps....then adding SF security is much easier.

Hi Alex

I would have do it the other way around, Applications, then permissions to encapsulate all permissions per applications, probably that would make it easier to maintenance the security.

App A
  ->Permission Name
       -> Add
       -> Edit
       -> Delete

App B
  ->Permission Name
       -> Add
       -> Edit
       -> Delete

Edhy Rijo