|
|
 Data ONTAP® PowerShell Toolkit
|
Cmdlet: New-NcLdapClient
NAME
New-NcLdapClient
SYNOPSIS
Create a new Lightweight Directory Access Protocol (LDAP) client configurati
on for the cluster.
SYNTAX
New-NcLdapClient [-Name] <String> [-Schema] <String> -AdDomain <String> -Pre
ferredAdServers <String[]> [-DoNotBindAsCifsServer] [-TcpPort <Int32>] [-Que
ryTimeout <Int32>] [-MinBindLevel <String>] [-BindDn <String>] [-BindPasswor
d <String>] [-BaseDn <String>] [-BaseScope <String>] [-UserDn <String>] [-Us
erScope <String>] [-GroupDn <String>] [-GroupScope <String>] [-NetGroupDn <S
tring>] [-NetGroupScope <String>] [-Controller <NcController[]>] [-WhatIf] [
-Confirm] [<CommonParameters>]
New-NcLdapClient [-Name] <String> [-Schema] <String> -Servers <String[]> [-T
cpPort <Int32>] [-QueryTimeout <Int32>] [-MinBindLevel <String>] [-BindDn <S
tring>] [-BindPassword <String>] [-BaseDn <String>] [-BaseScope <String>] [-
UserDn <String>] [-UserScope <String>] [-GroupDn <String>] [-GroupScope <Str
ing>] [-NetGroupDn <String>] [-NetGroupScope <String>] [-Controller <NcContr
oller[]>] [-WhatIf] [-Confirm] [<CommonParameters>]
DESCRIPTION
Create a new Lightweight Directory Access Protocol (LDAP) client configurati
on for the cluster.
PARAMETERS
-Name <String>
The name of the LDAP client configuration.
Required? true
Position? 1
Default value
Accept pipeline input? true (ByPropertyName)
Accept wildcard characters? false
-Schema <String>
LDAP schema to use for this configuration. The list of possible schemas
can be obtained using the Get-NcLdapClientSchema cmdlet.
Required? true
Position? 2
Default value
Accept pipeline input? true (ByPropertyName)
Accept wildcard characters? false
-AdDomain <String>
The Active Directory Domain Name for this LDAP configuration. The option
is ONLY applicable for configurations using Active Directory LDAP serve
rs.
Required? true
Position? named
Default value
Accept pipeline input? true (ByPropertyName)
Accept wildcard characters? false
-PreferredAdServers <String[]>
Preferred Active Directory (AD) Domain controllers to use for this confi
guration. This option is ONLY applicable for configurations using Active
Directory LDAP servers
Required? true
Position? named
Default value
Accept pipeline input? true (ByPropertyName)
Accept wildcard characters? false
-DoNotBindAsCifsServer
If specified, the cluster will not use the CIFS server's credentials to
bind to the LDAP server.
Required? false
Position? named
Default value
Accept pipeline input? true (ByPropertyName)
Accept wildcard characters? false
-TcpPort <Int32>
The TCP port on the LDAP server to use for this configuration. If omitte
d, this parameter defaults to 389.
Required? false
Position? named
Default value
Accept pipeline input? true (ByPropertyName)
Accept wildcard characters? false
-QueryTimeout <Int32>
Maximum time in seconds to wait for a query response from the LDAP serve
r. The default for this parameter is 3 seconds.
Required? false
Position? named
Default value
Accept pipeline input? true (ByPropertyName)
Accept wildcard characters? false
-MinBindLevel <String>
The minimum authentication level that can be used to authenticate with t
he LDAP server. If omitted, this parameter defaults to 'sasl' if the con
figuration uses Active Directory LDAP. For configurations that use LDAP
servers from other vendors, this parameter defaults to 'simple' if BindD
n is specified and 'anonymous' otherwise. Possible values:
"anonymous" - Anonymous bind
"simple" - Simple bind
"sasl" - Simple Authentication and Security Layer (SASL) bind
Required? false
Position? named
Default value
Accept pipeline input? true (ByPropertyName)
Accept wildcard characters? false
-BindDn <String>
The Bind Distinguished Name (DN) is the LDAP identity used during the au
thentication process by the clients. This is required if the LDAP server
does not support anonymous binds. This field is not used if BindAsCifsS
erver is specified. Example : cn=username,cn=Users,dc=example,dc=com
Required? false
Position? named
Default value
Accept pipeline input? true (ByPropertyName)
Accept wildcard characters? false
-BindPassword <String>
The password to be used with the BindDn.
Required? false
Position? named
Default value
Accept pipeline input? true (ByPropertyName)
Accept wildcard characters? false
-BaseDn <String>
Indicates the starting point for searches within the LDAP directory tree
. If omitted, searches will start at the root of the directory tree.
Required? false
Position? named
Default value
Accept pipeline input? true (ByPropertyName)
Accept wildcard characters? false
-BaseScope <String>
This indicates the scope for LDAP search. If omitted, this parameter def
aults to 'subtree'. Possible values:
"base" - Search only the base directory entry
"onelevel" - Search the base directory entry and the children of the ba
se entry
"subtree" - Search the base directory entry and all its descendants
Required? false
Position? named
Default value
Accept pipeline input? true (ByPropertyName)
Accept wildcard characters? false
-UserDn <String>
The User Distinguished Name (DN), if specified, is used as the starting
point in the LDAP directory tree for user lookups. If this parameter is
omitted, user lookups will start at the BaseDn.
Required? false
Position? named
Default value
Accept pipeline input? true (ByPropertyName)
Accept wildcard characters? false
-UserScope <String>
This indicates the scope for LDAP search when doing user lookups. Possib
le values:
"base" - Search only the base directory entry
"onelevel" - Search the base directory entry and the children of the ba
se entry
"subtree" - Search the base directory entry and all its descendants.
Required? false
Position? named
Default value
Accept pipeline input? true (ByPropertyName)
Accept wildcard characters? false
-GroupDn <String>
The Group Distinguished Name (DN), if specified, is used as the starting
point in the LDAP directory tree for group lookups. If not specified, g
roup lookups will start at the BaseDn.
Required? false
Position? named
Default value
Accept pipeline input? true (ByPropertyName)
Accept wildcard characters? false
-GroupScope <String>
This indicates the scope for LDAP search when doing group lookups. Possi
ble values:
"base" - Search only the base directory entry
"onelevel" - Search the base directory entry and the children of the ba
se entry
"subtree" - Search the base directory entry and all its descendants
Required? false
Position? named
Default value
Accept pipeline input? true (ByPropertyName)
Accept wildcard characters? false
-NetGroupDn <String>
The Netgoup Distinguished Name (DN), if specified, is used as the starti
ng point in the LDAP directory tree for netgroup lookups. If not specifi
ed, netgroup lookups will start at the BaseDn.
Required? false
Position? named
Default value
Accept pipeline input? true (ByPropertyName)
Accept wildcard characters? false
-NetGroupScope <String>
This indicates the scope for LDAP search when doing netgroup lookups. Po
ssible values:
"base" - Search only the base directory entry
"onelevel" - Search the base directory entry and the children of the ba
se entry
"subtree" - Search the base directory entry and all its descendants
Required? false
Position? named
Default value
Accept pipeline input? true (ByPropertyName)
Accept wildcard characters? false
-Controller <NcController[]>
A clustered Data ONTAP controller to receive this cmdlet, as embodied by
an NcController object. This parameter is returned by the Connect-NcCo
ntroller cmdlet. If not specified, the value in the global variable Cur
rentNcController is used. In the latter case, if CurrentNcController co
ntains a collection of NcController objects, this cmdlet is invoked on e
ach controller in succession.
Required? false
Position? named
Default value
Accept pipeline input? true (ByValue, ByPropertyName)
Accept wildcard characters? false
-WhatIf
Required? false
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-Confirm
Required? false
Position? named
Default value
Accept pipeline input? false
Accept wildcard characters? false
-Servers <String[]>
List of LDAP Server IP addresses to use for this configuration. The opti
on is NOT applicable for configurations using Active Directory LDAP serv
ers.
Required? true
Position? named
Default value
Accept pipeline input? true (ByPropertyName)
Accept wildcard characters? false
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer and OutVariable. For more information, type,
"get-help about_commonparameters".
INPUTS
OUTPUTS
DataONTAP.C.Types.Ldap.LdapClient
NOTES
Category: ldap
API: ldap-client-create
Family: cluster
-------------- Example 1 --------------
C:\PS>New-NcLdapClient -Name client_config -Schema AD-SFU -PreferredAdServe
rs 192.168.0.56 -AdDomain testing
Create a new LDAP client using an active directory LDAP server.
AdDomain : testing
BaseDn : DC=testing
BaseScope : subtree
BindAsCifsServer : True
BindDn :
BindPassword :
GroupDn :
GroupScope : subtree
LdapClientConfig : client_config
MinBindLevel : sasl
NcController : 192.168.182.144
NetgroupDn :
NetgroupScope : subtree
PreferredAdServers : {192.168.0.56}
QueryTimeout : 3
Schema : AD-SFU
Servers :
TcpPort : 389
UserDn :
UserScope : subtree
BindAsCifsServerSpecified : True
QueryTimeoutSpecified : True
TcpPortSpecified : True
RELATED LINKS
Get-NcLdapClient
Set-NcLdapClient
Remove-NcLdapClient
| Copyright © 2012 NetApp. All rights reserved. Use is subject to license terms. |
|
Data ONTAP® PowerShell Toolkit
|