Somebody knows how to change the user account and authentication method sharepoint uses to connect to its content database?
It is now setup to connect using Windows Integrated Authentication but I want to change that to a local user account.
Is it even possible to do this?
Thanks in advance
SharePoint supports both types of authentication in SQL Server:
Windows authentication (the default and preferred choice) - windows credentials are used to authenticate against the SQL server. SharePoint uses IIS which runs sites in an application pool worker process. You can change the credentials for a Web application pool here:
Central Administration > Operations > Service Accounts
SQL authentication - a username/password combination is created and stored in SQL server. When you create a content database you can choose SQL authentication and then provide the username/password (which you have already created in SQL). If you want to change the auth type of an existing database, you can detach it by checking the remove option on the database settings page (it removes the database from SharePoint but does not delete the actual data). Then you can re-attach the existing database and choose a different auth type. You can manage content databases here:
Central Administration > Application Management > Content Databases
you can do it by extending webapplication
The below links will helps you
http://weblog.vb-tech.com/nick/archive/2006/06/14/1617.aspx
http://www.codeproject.com/KB/sharepoint/moss_enableforms.aspx
Related
I just recently started to use Azure Data Studio to replace SSMS and VS Code. So far it is working great. I do have one "issue" I was wondering if anyone else encounters. I run the application with my Azure AD Admin. Under Connections I see all of my subscriptions and the underlying databases:
When I try to expand a server, I get an error that it is trying to connect with a SQL account:
It then brings up the connection details where it is set to use SQL Authentication:
If I change the Authentication type to Azure Active Directory - Universal with MFA support, and click connect it does without issue.
My question is, is there a way to change what the server connection uses as a default so I don't have to try to expand, fail, change auth type, and then connect? It is nice not having to manually create all of the connections to all of our subscriptions and sql servers and just have them load there and open them.
I searched all the settings of Azure data studio, but did not find the option to change the default authentication type of login Azure SQL.
User and workspace setttings of Azure data studio, you can refrence this document.
You can click the power plug icon in the right and then choose Authentication type to login to the server.
I am working on a task where I need to run SSRS and SharePoint on different servers, but right now, SSRS is working in integrated mode. Is it possible to configure a remote SSRS instance in integrated mode with a sharepoint instance ?
I stand under correction, however, I believe you could use the SharePoint SSRS web-part component and as long as the user executing the request (Your service account on SharePoint) has access to the database it should work.
Ensure that the AD user that is running the SharePoint front-end has access to the database (read / execute) - can be added to a group that has access to the database, or
give the user exclusive access to the database <- not the recommended solution
I've made a simple form in infopath, that looks up information in SQL server.
Using the design tool, I can fill in the form and submit it. All info from SQL server is being retrieved.
The SQL server is used in many different scenario's and accessible through different means. In the first phase I'm using a read/write account to connect to the database.
When I publish it to sharepoint (2010), I get an error the first time the SQL data is being requested.
I get an error that refers to the windows error logs; but I do not have access to the sharepoint environment.
The sharepoint is installed in the same forest, it should be able to get a connection to our sql server.
are the BCS (business connectivity services) necessary for this kind of action?
are there any other reasons why this could fail?
If it's working on your machine in debug mode but not on the server I would check two settings:
Authentication settings as you might be getting a double hop problem.
Security on database, make sure the user has access to the database
I set up a test Sharepoint 2007 Server before I set up a test AD Server to add it to. Based on what I read I did this backwards and if I would have set it up the other way around Sharepoint would use AD by default.
Is there a way I can change the configuration so this Sharepoint server will authenticate against the domain?
I did some searches in the configuration as well as SO and Google and couldn't come up with anything obvious.
Thanks!
You'll have to move your server into the new AD domain. Optionally you can change all the accounts that are used by SharePoint services to domain accounts, see http://support.microsoft.com/kb/934838. SharePoint will continue to work with local accounts though.
For any user rights assignment you did using local server accounts you can run the command: stsadm -o migrateuser to migrate user accounts from local\user to domain\user.
We're trying to setup an internet facing WSS 3.0 site without Active Directory. We have a single WFE and a single SQL Server (2005). The WFE will be outside our DMZ.
We've successfully created the Central Admin site with a local admin account on the WFE and a separate account on the SQL server for the database, but we're stuck on setting up the WSS search capability.
I couldn't seem to get things to work when using Central Admin to start the WSS Search service. I'm thinking I'll need to use stsadm -spsearch to set up the WSS search manually, rather than using the menus in Central Admin.
Does anyone have any tips and/or resources they recommend?
You want to setup your WSS3 site using Forms Based AUthentication, with an ASP.Net SQL Membership Provider and backend database.
Microsoft have a very nice guide on MSDN.
I followed this guide when attempting something similar. This explains how to allow forms based and AD authentication on the same site but you could just follow the parts that explain how to setup forms based.
This also includes changing the web.config file for central administration so that it can access the SQL database used to store users for forms based authentication.
It is very easy to follow.
We're looking for the same... rather we have a separate AD for our DMZ, however, for the extranet, would like to use it without AD accounts. May I ask what you've come up with so far?
Have seen posts talking about local machine accounts, but we do have 2 app servers and realize the maintenance involved to keep them in sync if we use local machine acounts. Swore I saw a 3rd party tool that would allow user's to be added into their own db and managed through their web-part/portal but can't seem to find it now.