sc250072 opened a new pull request, #69136:
URL: https://github.com/apache/airflow/pull/69136
This PR introduces a pluggable authentication framework to the Teradata
provider, enabling support for multiple authentication mechanisms including
native Teradata (TD2) and LDAP.
### Changes
New Authentication Framework
(providers/teradata/src/airflow/providers/teradata/auth/)
1. base.py: Abstract TeradataAuthMechanism base class
2. td2.py: Native Teradata (TD2) authentication (default)
3. ldap.py: New LDAP authentication support
4. registry.py: Mechanism registry for dynamic auth provider lookup
### Enhanced Teradata Hook
1. Refactored _get_conn_config_teradatasql() to use authentication registry
2. New _add_shared_connection_params() for SSL/TLS and transaction mode
config
3. Updated sqlalchemy_url property to carry logmech parameter
### Documentation Updates
1. Added LDAP authentication configuration examples
2. Documented logmech parameter and connection URI format
3. Added Port field documentation
### Bug Fix
1. teradata_to_teradata.py: Fixed cursor.execute() when sql_params is empty
### Comprehensive Tests
1. Auth mechanism tests (TD2, LDAP, registry)
2. Hook integration tests with LDAP and logdata support
### Configuration Example
LDAP Authentication:
JSON
{
"logmech": "LDAP",
"sslmode": "verify-ca",
"sslca": "/tmp/server-ca.pem"
}
### Backward Compatibility
✅ Fully backward compatible - TD2 remains default when logmech is not
specified.
**Teradata Provider System Health Dashboard**:
https://teradata.github.io/airflow/
**Teradata Provider documentation build status:**
https://github.com/Teradata/airflow/actions/workflows/ci-teradata-push-branch-documentation-unit-tests.yml
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
<!--
Thank you for contributing!
Please provide above a brief description of the changes made in this pull
request.
Write a good git commit message following this guide:
http://chris.beams.io/posts/git-commit/
Please make sure that your code changes are covered with tests.
And in case of new features or big changes remember to adjust the
documentation.
For user-facing UI changes, please attach before/after screenshots (or a
short
screen recording) so reviewers can assess the visual impact.
Feel free to ping (in general) for the review if you do not see reaction for
a few days
(72 Hours is the minimum reaction time you can expect from volunteers) - we
sometimes miss notifications.
In case of an existing issue, reference it using one of the following:
* closes: #ISSUE
* related: #ISSUE
-->
---
##### Was generative AI tooling used to co-author this PR?
<!--
If generative AI tooling has been used in the process of authoring this PR,
please
change below checkbox to `[X]` followed by the name of the tool, uncomment
the "Generated-by".
-->
- [ ] Yes (please specify the tool below)
<!--
Generated-by: [Tool Name] following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
-->
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information. Note: commit author/co-author name and email in commits
become permanently public when merged.
* For fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
