April 6, 2011 at 8:16 am
My team is using SharePoint 2007. We are currently considering using a centralized SQL Server database (2008) to handle everything for SharePoint 2007 so it would be centralized. In addition, we would like to handle the security there as well. Do you know of any place on the web that this is addressed or a vendor who has a 3rd party tool? If somebody has already created this there is no need to start from scratch.
April 6, 2011 at 8:26 am
What security are you referring to? The application accounts that SharePoint 2007 requires or user accounts?
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
April 6, 2011 at 8:49 am
Yes, I am aware that SharePoint uses different accounts. It could be handled the same way in SQL. The problem we are having is configuration management and maintenance issues. There are a couple apps that were created by a contractor. These apps are published to different sites. So whenever there is a change to the app, we have to go to every site and make the change. We want to create one site so we can make one change. To do that, we want to use our own database and not SharePoints. If we go this route, we would also have to put the security there as well. So we our trying figure out the best way of doing it in the database.
April 6, 2011 at 9:59 am
Security in a database is usually handled by creating Windows groups and then add those to database roles in SQL Server that control what access/permissions are allowed in the database.
The way it sounds you are wanting to pull the application out of SharePoint and make it a stand alone application/web app?
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
April 6, 2011 at 11:05 am
We were considering creating table in SQL and handing permissions that way.
April 6, 2011 at 1:01 pm
Sorry, but I'm confused by your post. Are you trying to maintain end-user access controls to SharePoint sites, etc. using a SQL table directly? Could you accomplish your goal by using Forms-Based Authentication or are you looking for something more granular?
April 6, 2011 at 1:47 pm
We are building web apps to be used for our enterprise that will be integrated within SharePoint. Meaning, we will use .net code, web parts, event handlers and the external SQL database in conjunction with the content database within SharePoint for the central site we setup for the users to interface to. We still want them to be able to use all of the SP functionality such as libraries, lists, workspaces...However, because of the nature of our enterprise, and the sanity of the technical team, we need a better approach for configuration management of the applications we deploy. Our thought is to use SP and an external DB to house all of the data captured from forms and then use this data for workflow, reports, forms...However, we need granular level security. We need to be able to secure information to the user level when they want to change data, add data, delete data, report on data and simply view data. We don't think there is a way to use their SP permissions/group permissions in a way that we can pass them to the SQL DB.
So, we are wondering if there is a way to do this where either we use a combination of security/permissions from SP and the DB, use one set of the permissions or create a totally new model and implement it such that it covers both? Has this been done?
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply