| .NET Security |
| C# Corner |
| I basically wanted to programmatically check whether the user had the relevant permissions by accessing their windows account. Fortunately, .NET provides this through the System.Security.Principal namespace. I also wanted to deny access to particular drives - this is done through the namespace System.Security.Permissions. |
|
| A System.Security.SecurityException exception occurs when you try to impersonate a user from a secondary thread in an ASP.NET Web application |
| http://www.kbalertz.com/ |
| (842790) - Explains that a SecurityException exception may occur when you try to impersonate a user from a secondary thread in an ASP.NET Web application. Describes three workarounds to solve this problem. |
|
| A System.Security.SecurityException exception occurs when you try to impersonate a user from a secondary thread in an ASP.NET Web application |
| http://www.kbalertz.com/ |
| (842790) - Explains that a SecurityException exception may occur when you try to impersonate a user from a secondary thread in an ASP.NET Web application. Describes three workarounds to solve this problem. |
|
| BUG: IWAM Account Is Not Granted the Impersonate Privilege for ASP.NET 1.1 on a Windows 2000 Domain Controller with SP4 |
| http://www.kbalertz.com/ |
| (824308) - When you install ASP.NET 1.1 on a computer running on a Windows 2000 Server domain controller with Service Pack 4 (SP4) installed, the IWAM account is not granted impersonate user rights for ASP.NET 1.1. When you request an ASP.NET 1.1 page, you may... |
|
| BUG: IWAM Account Is Not Granted the Impersonate Privilege for ASP.NET 1.1 on a Windows 2000 Domain Controller with SP4 |
| Microsoft Support |
| (824308) - When you install ASP.NET 1.1 on a computer running on a Windows 2000 Server domain controller with Service Pack 4 (SP4) installed, the IWAM account is not granted impersonate user rights for ASP.NET 1.1. When you request an ASP.NET 1.1 page, you may... |
|
| Custom Security Implementation |
| C#Today |
| In the previous articles in this series, we have discussed the security architectures and schemes available to developers in the .NET framework. Code access security and role based security are the two main types of security available to developers. In this article, Kaushal Sanghavi explores .NETs support for building a custom security scheme by implementing our own identity and principal classes that rely on user information stored in a database. In the previous article on Custom Security Permissions, we focused on Code Access Security, while in this article we focus on extending .NETs support for Role Based Security. |
|
| High-Performance .NET Application Development & Architecture |
| DotNetJunkies |
| It has always been a goal of project architects to plan an effective strategy from the ground up in regards to an new application. All relevant factors are taken into consideration with respect to the application, from its design and layout to a functional website infrastructure. |
|
| How to validate Windows user rights in a Visual Basic .NET application |
| http://www.kbalertz.com/ |
| (841699) - Describes how to verify the user's Windows user account and password in a Visual Basic .NET application. Uses the LogonUser Win32 API to verify the user name and password. |
|
| How to validate Windows user rights in a Visual Basic .NET application |
| http://www.kbalertz.com/ |
| (841699) - Describes how to verify the user's Windows user account and password in a Visual Basic .NET application. Uses the LogonUser Win32 API to verify the user name and password. |
|
| Implementing .NET Role-Based Security without COM+ |
| Egg Head Cafe |
| Security is important. Most developers don't like security. It requires a lot of thought. It requires study. Most developers would rather just "write code", and leave security to "somebody else". Unfortunately, if you are a developer and your job is to produce an application, then guess who that "somebody else" usually is? It's YOU. Even behemoth Microsoft got the message loud and clear. They've made security the single most important thing, above everything else. Wanna know why .NET Server, which was supposed to be released back in March, is delayed until the third quarter? Security! They weren't satisfied, and so they went back to the drawing board, so to speak. And its for real, too. The Microsoft insiders with whom I am privileged to speak with from time to time are totally focused on security. |
|
| Implementing Role-Based Security with ASP.NET |
| 4Guys from Rolla |
| In my previous article, I demonstrated how authentication providers can be used to manage the process of authenticating users. I also showed that classes and methods exist within the .NET Framework that can be used to inspect the basic attributes of a current user. In this article, I will extend upon that base, by showing how the .NET Framework provides support for the implementation of role based security. |
|
| INFO: Implementing Impersonation in an ASP.NET Application (Q306158) |
| http://www.kbalertz.com/ |
| This article describes different ways to implement impersonation in an ASP.NET application. |
|
| Quick editor for MCMS Postings |
| The Code Project |
| Quickly navigate through your channels and postings and edit the rawcontent of posting placeholders |
|
| You receive a "logon failure: unknown user name or bad" error message while accessing remote security-enhanced resources from an ASP.NET application |
| http://www.kbalertz.com/ |
| (842789) - Discusses the problem of not being able to access a security-enhanced remote resource from an ASP.NET application. Describes several workarounds for this problem. |
|
| You receive a "logon failure: unknown user name or bad" error message while accessing remote security-enhanced resources from an ASP.NET application |
| http://www.kbalertz.com/ |
| (842789) - Discusses the problem of not being able to access a security-enhanced remote resource from an ASP.NET application. Describes several workarounds for this problem. |
|
