Authentication Cascading, which was introduced in Aster Database 6.0™, enables you to omit the username and password when issuing SQL and function calls from the ACT Command Line (SQL prompt), from SQL scripts, and when connecting through JDBC or ODBC.
The key features of Authentication Cascading include:
- Support for Teradata Aster SQL-MapReduce® functions.
- The ability to execute Teradata Aster SQL-MapReduce® functions without including the username and password in the user script.
- The ability to hide username and password from SQL statements that invoke JDBC driver functions in the Aster Analytics Foundation.
- The ability to write driver functions that do not require authentication credentials (this includes SSO, LDAP or username/password).
- The ability to use the authenticated context from which the Teradata Aster SQL-MapReduce® function was invoked to re-authenticate with when connecting back via the JDBC or ODBC driver.
- Authentication Cascading allows the user to connect to a different database, provided the user is authorized to connect to it, as long as it is in the same cluster.
- When using Authentication Cascading, if you do not specify a database and port, these are taken to be the default on the Aster Database you are currently connected to.