In a Windows domain, SSPI can be used on Windows-based computers without a Kerberos client installed on the client computer. Windows domain accounts already have associated Kerberos principals.
SSPI can only be used by SQL Anywhere clients in the Kerberos connection parameter. SQL Anywhere database servers cannot use SSPI—they need a supported Kerberos client other than SSPI.
Set up Kerberos authentication. See Setting up Kerberos authentication.
Start the SQL Anywhere server with the -krb option to enable Kerberos authentication. For example:
dbeng12 -krb -n my_server_princ C:\kerberos.db |
Change the public or temporary public option login_mode to a value that includes Kerberos. You must have DBA authority to set this option. For example:
SET OPTION PUBLIC.login_mode = 'Kerberos'; |
Create a database user ID for the client. (Optionally, you can use an existing database user ID for the Kerberos login, as long as that user has the correct permissions.) For example:
CREATE USER kerberos_user IDENTIFIED BY abc123; |
Create a mapping from the client's Kerberos principal to an existing database user ID by executing a GRANT KERBEROS LOGIN TO statement. This statement requires DBA authority. For example:
GRANT KERBEROS LOGIN TO "pchin@MYREALM.COM" AS USER "kerberos_user"; |
Connect to the database from the client computer. For example:
dbisql -c "KERBEROS=SSPI;Server=my_server_princ" |
When Kerberos=SSPI is specified in the connection string, a Kerberos login is attempted.
A connection attempt using the following Interactive SQL statement will also succeed, providing the user has logged on with a user profile name that matches a Kerberos login mapping in a default database of a server:
CONNECT USING 'KERBEROS=SSPI'; |
Discuss this page in DocCommentXchange.
|
Copyright © 2012, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.1 |