Last post Jul 17, 2010 04:51 AM by minhquan
Mar 24, 2010 06:23 PM|brianwoodring|LINK
I can't seem to create a simple forms authentication (un/pw stored in web.config) that will work with Dynamic Data. Does it require SQL-stored credential management? The login (using asp.net 2 control) works; but the "second" layer of security built into
DD prevents loading the table list page, yielding this error:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to
allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
The server is available, the connection string is valid, and DD works so long as I don't put a forms authentication in front of it. Is DD in fact incompatible with web.config stored credentials?
Mar 24, 2010 11:30 PM|Sarahn|LINK
forms authentication can be db based if you set it to. you can just make direct queries to your database in your login button event and validate the scredentials manually, if they are goood then you can call the formsauthentication.redirectfromloginpage.
however if you have given querystring for formsauthentication then you will have to use formsauthentication.validate and it shall validate from database or web.config depending on your setting. i suggest you going through a forms authentication article first
before going into it. here are a few to look at.
Mar 25, 2010 02:14 AM|brianwoodring|LINK
Seems to have been a problem with the ASP 2.0 Login control. Once I removed it, and replaced it with simpler html, the Dynamic Data start page it directs to (upon successful authentication) rendered fine.
Mar 25, 2010 08:02 PM|sjnaughton|LINK
try this sample Securing Dynamic Data Preview 4 Refresh – Part 1 the routing part of the sample witll work with DD1
Jul 17, 2010 04:51 AM|minhquan|LINK
to brianwoodring: Hi, I have the same problem with you. I don't know what is exactly implemented in Login control that make Login control failed