You searched for the word(s): userid:801669

More Search Options

RSS Available

• Re: Using Membership Provider w/Linked Server

  Ok, I spoke too soon. For some reason, the above seemed to work on our DEV box a couple of times, then all we got were errors. This was discovered when we tried it with the PROD DMZ server and went back to DEV for a sanity check. I will keep searching; I'm not yet convinced this can not be done.

  Posted to Security (Forum) by pearsonbe on 6/10/2009

• Re: Using Membership Provider w/Linked Server

  Changing the connection string from this: <add name=" AppName " connectionString="Data Source= DMZSERVER ; User ID= AppUserName ; Password= AppPwd ; Initial Catalog= Accounts "/> to this: <add name=" AppName " connectionString="Data Source= DMZSERVER.DBNAME.DBO. ; User ID= AppUserName ; Password= AppPwd "/> solved the problem. The key is fully qualifiying the data source and removing the Initial Catalog specification - Easy. Greg

  Posted to Security (Forum) by pearsonbe on 6/5/2009

• Re: Using Membership Provider w/Linked Server

  Thanks for responding Wencui. I'm sorry mine is so late. What details do you need? Here are the basics: Outside the firewall 1. ASP.NET application hosted in IIS 2. SQL Server database that contains the Membership objects (tables, stored procs, views) 3. A linked server connection Inside the firewall 1. SQL Server database that contains the application objects and data (tables, stored procs, views) Configuration Connection string, RoleManager, Membership, Forms <connectionStrings> <add

  Posted to Security (Forum) by pearsonbe on 6/5/2009

• Re: Setting Membership/Profile/Role provider's connection string at runtime...?

  Thanks. I got it to work. There must have been a problem in the C# to VB translation. Now, I'm trying to get Memebership access to work with a Linked Server. I haven't found a solution for this yet.

  Posted to Security (Forum) by pearsonbe on 5/8/2009

• Re: Using Membership Provider w/Linked Server

  Andrew, that's exactly my intent; however, I'd rather not expose my account information in the DMZ. I want to house the account information in a separate database behind the firewall. Do you have an example that uses web services for Membership access? I thought I found something that would work on CodeProject: http://www.codeproject.com/KB/aspnet/WSSecurityProvider.aspx I read it carefully but never saw where a connection string was provided for Membership access. And my attempts to contact

  Posted to Security (Forum) by pearsonbe on 5/8/2009

• Re: Using Membership Provider w/Linked Server

  Sorry, there was an error and this posted twice.

  Posted to Security (Forum) by pearsonbe on 5/8/2009

• Re: Using Membership Provider w/Linked Server

  Currently, the project has membership configured in the web.config the standard way: <connectionStrings> <add name="LT" connectionString="Data Source=ProtectedServer;User ID=User;Password=Pwd;Initial Catalog=LT_Accounts"/> </connectionStrings> <roleManager enabled="true" cookieTimeout="20" cookieSlidingExpiration="true"> <providers> <clear/> <add connectionStringName="LT" applicationName="LT"

  Posted to Security (Forum) by pearsonbe on 5/8/2009

• Using Membership Provider w/Linked Server

  I'm having a hard time finding a solution to this problem. I have an application that is hosted in a DMZ and uses a linked server to access data in an internal database (behind a firewall). Currently, I have just the tables and procs needed to authenticate the user in the DMZ. The rest of the database and data exist on the internal server. I was forced to do this because it seems the Membership controls/system need direct access to the database. I haven't found an example of an authentication

  Posted to Security (Forum) by pearsonbe on 5/5/2009

• Re: Setting Membership/Profile/Role provider's connection string at runtime...?

  Thanks, Gewgala. I know it's been a while since you responded, but I finally got back to this in my project. The C# code code works fine as you and others have stated. The code I converted to VB works for the Membership provider, but not the RoleProvider. I don't know why. Of course, it could be something with the translation. I'm not up on reflection yet. Next, up is finding a way to integrate this with our shops standard data access layer. I found a good article on another site that

  Posted to Security (Forum) by pearsonbe on 3/5/2009

• Re: Setting Membership/Profile/Role provider's connection string at runtime...?

  Gewgala, so you didn't have any issues? I still haven't had it work in the VB version I created so I think I'll try using the exact code in C#.

  Posted to Security (Forum) by pearsonbe on 1/12/2009