The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
Row Level Security Help
Posted: 02 May 06 6:22 PM
|
fiogf49gjkf0d Hello,
Does anyone know if SLX supports row level security. We have developed a set of HR & recruiting customizations for internal use and Contacts that are actually employees are accessible by both recruiting and HR. The problem this creates is that recruiters are not allowed to see activities, histories, and attachements created by HR. So I need a way to restrict their access. I have investigated filtering out records in the SQL statements used by the histories and attachments, but doing so at that level still allows the recruiter to craft a search against the history table and see the information. Not to mention, I don't think I can access the activites form to change the SQL there.
We are running SLX 6.2.3 on MSSQL 2000.
One solution I came up with is described below, To me, it's a really ugly hack, as I have to modify a stored procedure from the master MSSQL database to make it work. I'm hoping there is a better solution, but I'm not seeing anything on the internet to indicate that there is. Please help.
I was able to establish row-level security by creating a new blank database and creating external views in the new db pointing to all the tables in my slx database. That looked all and good until during testing, I found that doing so causes the SLX security to shut down and all records are accessable by everyone, no matter who they were owned by. It appears that when SLX starts, it does a check to see if the Account table is actually a table or a view. If it's a view, then no security, if it's reported as a table then everything is good. What I did to get around this was to take a copy of the sp_table_rowset stored procedure from the master database and place it into my external view database and modified it to return the type of "Table" unless the last char in the table/view name is an underscore "_".
Please let me know if you have any information on Row-Level security that could help me. I'm wondering if the alias/synonym feature in MSSQL 2005 would help here, but I doubt it as the the owner sysdba is hard coded.
Thank you, ...Rob
|
|
|
|
Re: Row Level Security Help
Posted: 02 May 06 6:59 PM
|
fiogf49gjkf0d Add a column named SECCODEID to the tables that you want secured. Then populate the column with the appropriate team/user. This way the SalesLogix OLEDB Provider will enforce security for you.
Timmus |
|
|
|
Re: Row Level Security Help
Posted: 02 May 06 8:22 PM
|
buy naltrexone 3mg buy naltrexone online canada fiogf49gjkf0d Thanks for the reply.
I tried that, but SLX won't let me add any new columns to the History or Activity tables. I even tried adding a new 1 to 1 table called CEI_HistorySecurity that I inner joined to History table. In the CEI_HistoryTable, I added a seccodeid, but that didn't seem to have any impact.
...Rob |
|
|
|
Re: Row Level Security Help
Posted: 02 May 06 9:40 PM
|
buy ventolin inhaler uk buy ventolin nz where to buy abortion pill buy the abortion pill ru486 online click here fiogf49gjkf0d You will need to hack the system so you can add columns to stock tables. I suggest making the hack on a development database and using a bundle to add the column to your production system.
Timmus |
|
|
| |
|
Re: Row Level Security Help
Posted: 03 May 06 7:07 PM
|
fiogf49gjkf0d Open Enterprise Manager add the field, then bundle it, then drop the field, then apply the bundle (there are other ways too, but that one is the easiest) |
|
|
| |
|
Re: Row Level Security Help
Posted: 03 May 06 11:58 PM
|
fiogf49gjkf0d Originally posted by Ryan Farley
Open Enterprise Manager add the field, then bundle it, then drop the field, then apply the bundle (there are other ways too, but that one is the easiest) |
|
Thanks for the reply, Ryan. I was going to suggest that but wanted to test to ensure there werent defects with the bundler that would cause more harm than good.
Timmus |
|
|
|
Re: Row Level Security Help
Posted: 05 May 06 3:29 PM
|
fiogf49gjkf0d Timmus and Ryan,
I did what you suggested to create the field and then created a trigger to populate the it based on the business rules involed. Everything is working perfectly!
Thank Very Much for your Help!
|
|
|
|