You cannot use DSCC to perform this task. Use the command line, as described in this procedure.
Before using a client application that is enabled with the GSSAPI mechanism, initialize the Kerberos security system with your user Principal.
$ kinit user-principal
where the user-principal is your SASL identity, for example, firstname.lastname@example.org.
Specify SASL options for using Kerberos.
Note that in the UNIX environment, you must set the SASL_PATH environment variable to the correct path for the SASL libraries. For example in the Korn shell:
$ export SASL_PATH=SASL-library
This path assumes that Directory Server is installed on the same host where the LDAP tools are invoked.
The following example of the ldapsearch tool shows the use of the -o (lowercase letter o) option to specify SASL options for using Kerberos:
$ ldapsearch -h www.host1.com -p 1389 -o mech=GSSAPI -o authid="bjensen@EXAMPLE.COM" \ -o authzid="bjensen@EXAMPLE.COM" -b "dc=example,dc=com" "(givenname=Richard)"
The authid can be omitted because it is present in the Kerberos cache that was initialized by the kinit command. If authid is present, authid and authzid must be identical, although the authzid intended for proxy operations is not used. The value of authid is the Principal that is used in identity mapping. The Principal must be the full Principal, including the realm. See GSSAPI Identity Mappings.