Hi there,
Got a nice challenge here .. we must implement a security system, that should enable us to handle :
+ Application Security (that is, what sections of the application a user can “see” … menu options, screen controls and so on) and
+ Data Security (that is, what user the can see and or update).
In the case of data security, we need to be able to handle “data hierarchies”. That is, a user in the hierarchy can only see information related to them , their “sons”, their grandsons and so on , and of course, they cannot see the information of their parents and of their brothers in most cases (ahh what would be our world without exceptions). Nice thing is that we could have different hierarchies !
What we are using now is .Net 2003 and Sql Server 2000 .. we know that “Yukon” will have row level security, but we need the product to be stable before we can consider using it.
Another interesting challenge would be to implement this security on the database somehow, to make sure that all possible interface clients that access it would be see what they are allowed to see.
If you have any article or experience you can share about his, would be greatly appreciated
Thanks !
TF
Got a nice challenge here .. we must implement a security system, that should enable us to handle :
+ Application Security (that is, what sections of the application a user can “see” … menu options, screen controls and so on) and
+ Data Security (that is, what user the can see and or update).
In the case of data security, we need to be able to handle “data hierarchies”. That is, a user in the hierarchy can only see information related to them , their “sons”, their grandsons and so on , and of course, they cannot see the information of their parents and of their brothers in most cases (ahh what would be our world without exceptions). Nice thing is that we could have different hierarchies !
What we are using now is .Net 2003 and Sql Server 2000 .. we know that “Yukon” will have row level security, but we need the product to be stable before we can consider using it.
Another interesting challenge would be to implement this security on the database somehow, to make sure that all possible interface clients that access it would be see what they are allowed to see.
If you have any article or experience you can share about his, would be greatly appreciated
Thanks !
TF