Export (0) Print
Expand All

SqlClientPermission Class

Enables the .NET Framework Data Provider for SQL Server to help make sure that a user has a security level sufficient to access a data source.

Namespace:  System.Data.SqlClient
Assembly:  System.Data (in System.Data.dll)

[SerializableAttribute]
public ref class SqlClientPermission sealed : public DBDataPermission

The SqlClientPermission type exposes the following members.

  NameDescription
Public methodSqlClientPermission() Obsolete. Initializes a new instance of the SqlClientPermission class.
Public methodSqlClientPermission(PermissionState)Initializes a new instance of the SqlClientPermission class.
Public methodSqlClientPermission(PermissionState, Boolean) Obsolete. Initializes a new instance of the SqlClientPermission class.
Top

  NameDescription
Public propertyAllowBlankPasswordGets a value indicating whether a blank password is allowed. (Inherited from DBDataPermission.)
Top

  NameDescription
Public methodAddAdds a new connection string and a set of restricted keywords to the SqlClientPermission object. (Overrides DBDataPermission::Add(String, String, KeyRestrictionBehavior).)
Public methodAssertDeclares that the calling code can access the resource protected by a permission demand through the code that calls this method, even if callers higher in the stack have not been granted permission to access the resource. Using Assert can create security issues. (Inherited from CodeAccessPermission.)
Public methodCopyReturns the SqlClientPermission as an IPermission. (Overrides DBDataPermission::Copy().)
Public methodDemandForces a SecurityException at run time if all callers higher in the call stack have not been granted the permission specified by the current instance. (Inherited from CodeAccessPermission.)
Public methodDeny Obsolete. Prevents callers higher in the call stack from using the code that calls this method to access the resource specified by the current instance. (Inherited from CodeAccessPermission.)
Public methodEqualsDetermines whether the specified CodeAccessPermission object is equal to the current CodeAccessPermission. (Inherited from CodeAccessPermission.)
Public methodFromXmlReconstructs a security object with a specified state from an XML encoding. (Inherited from DBDataPermission.)
Public methodGetHashCodeGets a hash code for the CodeAccessPermission object that is suitable for use in hashing algorithms and data structures such as a hash table. (Inherited from CodeAccessPermission.)
Public methodGetTypeGets the Type of the current instance. (Inherited from Object.)
Public methodIntersectReturns a new permission object representing the intersection of the current permission object and the specified permission object. (Inherited from DBDataPermission.)
Public methodIsSubsetOfReturns a value indicating whether the current permission object is a subset of the specified permission object. (Inherited from DBDataPermission.)
Public methodIsUnrestrictedReturns a value indicating whether the permission can be represented as unrestricted without any knowledge of the permission semantics. (Inherited from DBDataPermission.)
Public methodPermitOnlyPrevents callers higher in the call stack from using the code that calls this method to access all resources except for the resource specified by the current instance. (Inherited from CodeAccessPermission.)
Public methodToStringCreates and returns a string representation of the current permission object. (Inherited from CodeAccessPermission.)
Public methodToXmlCreates an XML encoding of the security object and its current state. (Inherited from DBDataPermission.)
Public methodUnionReturns a new permission object that is the union of the current and specified permission objects. (Inherited from DBDataPermission.)
Top

The IsUnrestricted property takes precedence over the AllowBlankPassword property. Therefore, if you set AllowBlankPassword to false, you must also set IsUnrestricted to false to prevent a user from making a connection using a blank password.

NoteNote

When using code access security permissions for ADO.NET, the correct pattern is to start with the most restrictive case (no permissions at all) and then add the specific permissions that are needed for the particular task that the code needs to perform. The opposite pattern, starting with all permissions and then denying a specific permission, is not secure, because there are many ways of expressing the same connection string. For example, if you start with all permissions and then attempt to deny the use of the connection string "server=someserver", the string "server=someserver.mycompany.com" would still be allowed. By always starting by granting no permissions at all, you reduce the chances that there are holes in the permission set.

.NET Framework

Supported in: 4.6, 4.5, 4, 3.5, 3.0, 2.0, 1.1, 1.0

.NET Framework Client Profile

Supported in: 4, 3.5 SP1

Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012, Windows 7, Windows Vista SP2, Windows Server 2008 (Server Core Role not supported), Windows Server 2008 R2 (Server Core Role supported with SP1 or later; Itanium not supported)

The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.

Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.
Show:
© 2014 Microsoft