|
[x]
Posted via EE Mobile
|
||
Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again. |
||
| 07/09/2009 at 02:20PM PDT, ID: 24558267 |
|
[x]
Attachment Details
|
||
|
[x]
The Solution Rating System
|
||
With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.
Your Input Matters If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support. Thank you! |
||
1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: 20: 21: 22: 23: 24: 25: 26: 27: 28: |
I have this already
***This is in my web.config file***
</system.web>
<authentication mode="Windows"/>
<roleManager enabled="true" defaultProvider="AspNetWindowsTokenRoleProvider"/>
<identity impersonate="true" userName="Domain/XXXX" password="XXXXX"/>
</system.web>
<webServices>
<authenticationService enabled="true" requireSSL="false"/>
</webServices>
**This is my authetication code in my program**
if (Roles.IsUserInRole(@"Domain\XXXX"))
{
}
else
{
Response.Redirect("http://Server/UnauthorizedAccess.aspx");
}
|
Advertisement
