- database_name.
- user_dbname.
- Optional name of the location where the authorization is to be stored.
- authorization_name
- Name for the authorization object. This must be a unique name within the database where the name is stored.
- INVOKER
- DEFINER
- If specifying INVOKER TRUSTED, or TRUSTED alone, Teradata creates the authorization object in the database of the user who creates the object. This syntax makes the authorization available only to those with privilege to the user database.
- If specifying DEFINER TRUSTED or DEFINER DEFAULT TRUSTED, Teradata creates the authorization object in the database that contains the object using the authorization; for a foreign server this is the TD_SERVER_DB database. This syntax makes the authorization globally available.
- TRUSTED
- A keyword used to specify that the credentials are encrypted and stored as database objects.
- 'fs_user_name'
- 'fs_user_name@realm_name'
- The name of the credential on the remote platform used by the foreign server.
The user name for the authorization object can consist of a user name alone or a user name and the name of the Kerberos realm. When only the user name is specified, the default realm specified in the krb5.conf file is used for kinit.
If including the Kerberos realm name, the default realm is ignored and the realm specified in the authorization object is used for kinit. Include a Kerberos realm name if you have one of the following situations:- You want users to be able to connect to multiple Kerberized clusters, each from a different realm, from the same Teradata system.
- You want users to be able to connect to a Kerberized cluster where the authentication realm is different from the service realm.
If used with the name of the Kerberos realm, the user_name portion cannot also contain an @ sign. - 'fs_password'
- The password for the credential on the remote platform used by the foreign server.