[ Smireni Magnet @ 23.08.2006. 08:34 ] @
Pravim malu intranet aplikaciju, za koju je potrebno omogućiti pristup autentikacijom preko active direktorijuma. Pratio sam msdn i napravio web.config fajl prema datim uputstvima. BTW, istu stvar savetuju i neki drugi izvori. Ali, don't lay devil, iliti ne lezi vraže, dobijam sledeću grešku: Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. Parser Error Message: Unable to establish secure connection with the server Source Error: Line 37: <add Line 38: name="MyADMembershipProvider" Line 39: type="System.Web.Security.ActiveDirectoryMembershipProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" Line 40: Line 41: connectionStringName="ADConnectionString" Source File: F:\Visual Studio 2005\Projects\alarms\PrecompiledWeb\alarms\web.config Line: 39 Šta bi to moglo da bude? Da li sam nešto zaboravio da setujem? Ovo je izgled celog mog web.config fajla: Code: <?xml version="1.0"?> <!-- Note: As an alternative to hand editing this file you can use the web admin tool to configure settings for your application. Use the Website->Asp.Net Configuration option in Visual Studio. A full list of settings and comments can be found in machine.config.comments usually located in \Windows\Microsoft.Net\Framework\v2.x\Config --> <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0"> <appSettings/> <connectionStrings> <add name="ADConnectionString" connectionString="LDAP://blah, blah/CN=Users,DC=blah, blah"/> </connectionStrings> <system.web> <!-- Set compilation debug="true" to insert debugging symbols into the compiled page. Because this affects performance, set this value to true only during development. --> <compilation debug="true"/> <!-- The <authentication> section enables configuration of the security authentication mode used by ASP.NET to identify an incoming user. --> <authentication mode="Forms"> <forms loginUrl="Login.aspx" protection="All" timeout="30" name="AppNameCookie" requireSSL="false" slidingExpiration="true" defaultUrl="Default.aspx" cookieless="UseCookies" enableCrossAppRedirects="false"/> </authentication> <authorization> <deny users="?"/> <allow users="*"/> </authorization> <membership defaultProvider="MyADMembershipProvider"> <providers> <add name="MyADMembershipProvider" type="System.Web.Security.ActiveDirectoryMembershipProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" connectionStringName="ADConnectionString" connectionUsername="blah\user" connectionPassword="password"/> </providers> </membership> <!-- The <customErrors> section enables configuration of what to do if/when an unhandled error occurs during the execution of a request. Specifically, it enables developers to configure html error pages to be displayed in place of a error stack trace. <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm"> <error statusCode="403" redirect="NoAccess.htm" /> <error statusCode="404" redirect="FileNotFound.htm" /> </customErrors> --> </system.web> </configuration> Unapred zahvalan, SM |