Put the windows authentication connection string manually into the web.config file (umbracoDbDSN) before you run the install, I get a feeling the install script will pick this up.
Ohh, but the problem now is that I have a development environment where you implement an entire web site and want to load in a server but the server database of the company policy does not allow me to change the authentication mode. is decisive is what I'm trying to migrate a site from one server to another.
I'm pretty sure Umbraco doesn't care which authentication you use for the db, as long as the connection string is valid.
So you can set up and install the database on your local machine using SQL Server authentication and then just change the web.config connection string to use your production servers authentication, then restore your local database back up to the production server.
Thousand Thanks John for your comments, but let me comment you what happened, I did exactly what you're telling me, modify the we.config to receive the parameters of the new database server.
And the only thing different with other migrations I've done, is that in this case the database server production environment is configured for Windows authentication, so I thought that was the problem. you've made similar migrations?, only modify the we.config?, I realize that other configurations to run the site developed in the new environment?.
The steps to perform are the basics.
1. Create a. Back to the database. 2. copy the entire folder where the newly developed site. 3. Create a new website in the new environment. and redirects it to the directory you just copied. 4. Restore the database. 5. Modify the wen.config, with the connection parameters of the new database., Instance name, name of database user and password, the username and password are Windows. and that user is mapping the database to restore the roles specified in the installation of Umbraco.
It's unfortunate that Umbraco requires a SQL authentication account to proceed with the setup wizard. Even though you can change the connection string later, this means you must set up your SQL Server with SQL authentication enabled (or mixed mode), which is not a best practice. Microsoft continues to support SQL authentication for legacy purposes, but enabling it is not a recommended practice (even if you don't use it).
Umbraco v4 SQL 2008 Windows Authentication Only?
Hi,
We are in the process on installing Umbraco v4 on Windows Server 2008 II7 SQL 2008. I have read the installation doc when installing SQL to choose:
"
Mixed Mode (Windows Authentication and SQL Server Authentication)"
Is it posible to install Umbraco on "Windows Authentication" mode only?
Any help would be appreciated,
Gerald
Hi Gerald,
AFAIK no, you should use sql authentication! Any use case why you'd prefer windows over sql authentication?
Cheers,
/Dirk
I Have same question, Umbraco CMS, support Windows Authentication Mode, please somebody can help me...
I don't know 100% but this may work:
Put the windows authentication connection string manually into the web.config file (umbracoDbDSN) before you run the install, I get a feeling the install script will pick this up.
Rich
Ohh, but the problem now is that I have a development environment where you implement an entire web site and want to load in a server but the server database of the company policy does not allow me to change the authentication mode. is decisive is what I'm trying to migrate a site from one server to another.
Fernado,
I'm pretty sure Umbraco doesn't care which authentication you use for the db, as long as the connection string is valid.
So you can set up and install the database on your local machine using SQL Server authentication and then just change the web.config connection string to use your production servers authentication, then restore your local database back up to the production server.
Rich
Thousand Thanks John for your comments, but let me comment you what happened, I did exactly what you're telling me, modify the we.config to receive the parameters of the new database server.
And the only thing different with other migrations I've done, is that in this case the database server production environment is configured for Windows authentication, so I thought that was the problem. you've made similar migrations?, only modify the we.config?, I realize that other configurations to run the site developed in the new environment?.
The steps to perform are the basics.
1. Create a. Back to the database.
2. copy the entire folder where the newly developed site.
3. Create a new website in the new environment. and redirects it to the directory you just copied.
4. Restore the database.
5. Modify the wen.config, with the connection parameters of the new database., Instance name, name of database user and password, the username and password are Windows. and that user is mapping the database to restore the roles specified in the installation of Umbraco.
I appreciate your comments.
Hey Fernando,
Seems about right to me, are you saying that it didn't work, do you get any errors?
Rich
Thanks Again!
Regards
It's unfortunate that Umbraco requires a SQL authentication account to proceed with the setup wizard. Even though you can change the connection string later, this means you must set up your SQL Server with SQL authentication enabled (or mixed mode), which is not a best practice. Microsoft continues to support SQL authentication for legacy purposes, but enabling it is not a recommended practice (even if you don't use it).
is working on a reply...