Authentication backends (LDAP, OAuth) in Apache Airflow - Step-by-Step Execution

Process Flow - Authentication backends (LDAP, OAuth)

User tries to login

↓

Select Auth Backend

↓

LDAP Backend

↓

Validate creds

↓

Success?

No→Fail Login

Yes↓

Grant Access

User login triggers selection of LDAP or OAuth backend, which validates credentials or redirects for OAuth, then grants or denies access.

Execution Sample

Apache Airflow

auth_backend = 'LDAP'
if auth_backend == 'LDAP':
    result = ldap_auth(username, password)
else:
    result = oauth_auth()
if result == 'success':
    grant_access()

This code chooses LDAP or OAuth authentication and grants access if successful.

Process Table

Step	Action	Auth Backend	Credentials Check	Result	Next Step
1	User submits login	LDAP	username/password provided	Pending	Check backend
2	Select backend	LDAP	N/A	N/A	Call ldap_auth()
3	Call ldap_auth()	LDAP	Verify username/password	success	Grant access
4	Grant access	LDAP	N/A	success	User logged in
5	End	LDAP	N/A	N/A	Stop execution

💡 User credentials verified by LDAP, login successful, execution ends.

Status Tracker

Variable	Start	After Step 2	After Step 3	Final
auth_backend	None	LDAP	LDAP	LDAP
result	None	None	success	success

Key Moments - 2 Insights

Why does the code call ldap_auth() only when auth_backend is 'LDAP'?

Because the execution_table row 2 shows backend selection, and only if 'LDAP' is chosen does the code call ldap_auth() to verify credentials.

What happens if ldap_auth() returns 'failure'?

Though not shown in this trace, the code would skip granting access and likely show a login failure message, as success is required to proceed (see row 3 and 4).

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'result' after Step 3?

A failure

B None

C success

D Pending

💡 Hint

Check the 'result' column in row 3 of the execution_table.

At which step does the system decide to grant access?

A Step 2

B Step 4

C Step 3

D Step 5

💡 Hint

Look at the 'Action' column and find when 'Grant access' happens in the execution_table.

If auth_backend was set to 'OAuth', which step would change in the execution_table?

A Step 2 would call oauth_auth() instead of ldap_auth()

B Step 3 would verify username/password

C Step 4 would deny access

D Step 5 would be skipped

💡 Hint

Refer to the concept_flow where OAuth backend redirects to OAuth provider instead of LDAP verification.

Concept Snapshot

Authentication backends in Airflow:
- Choose backend: LDAP or OAuth
- LDAP: verify username/password directly
- OAuth: redirect user to provider for login
- On success, grant access
- On failure, deny login
Simple if-else logic controls flow.

Full Transcript

This visual execution shows how Airflow handles authentication using backends like LDAP and OAuth. When a user tries to login, the system selects the authentication backend. If LDAP is chosen, it verifies the username and password directly. If OAuth is chosen, the user is redirected to an external provider for login. The execution table traces the steps for LDAP: user submits credentials, backend selection, LDAP verification, and granting access on success. Variables like 'auth_backend' and 'result' track the flow. Key moments clarify why ldap_auth() is called only for LDAP and what happens on failure. The quiz tests understanding of variable values and step actions. The snapshot summarizes the flow simply for quick recall.

Practice

1. What is the main purpose of configuring an authentication backend like LDAP or OAuth in Airflow?

easy

A. To schedule DAGs automatically

B. To verify users using external systems for better security

C. To store Airflow logs externally

D. To speed up Airflow task execution

Solution

1. Step 1: Understand authentication backend role

   Authentication backends connect Airflow to external user verification systems like LDAP or OAuth.

2. Step 2: Identify the main benefit

   This setup improves security and user management by using existing accounts outside Airflow.

3. Final Answer:

   To verify users using external systems for better security -> Option B

4. Quick Check:

   Authentication backend = user verification [OK]

Hint: Authentication backends verify users externally [OK]

Common Mistakes:

• Confusing authentication with task scheduling
• Thinking it speeds up task execution
• Assuming it stores logs

2. Which of the following is the correct way to specify the LDAP authentication backend in the airflow.cfg file?

easy

A. auth_backend = airflow.providers.ldap.auth.backend.LDAPAuthBackend

B. auth_backend = airflow.contrib.auth.backends.ldap_auth

C. auth_backend = airflow.www.auth.backend.ldap

D. auth_backend = airflow.contrib.auth.backends.ldap_auth_backend.LDAPBackend

Solution

1. Step 1: Recall the correct LDAP backend path

   The correct LDAP backend path in Airflow 2.x is airflow.providers.ldap.auth.backend.LDAPAuthBackend.

2. Step 2: Compare options

   auth_backend = airflow.providers.ldap.auth.backend.LDAPAuthBackend matches the correct syntax exactly; others have incorrect module paths or class names.

3. Final Answer:

   auth_backend = airflow.providers.ldap.auth.backend.LDAPAuthBackend -> Option A

4. Quick Check:

   Correct LDAP backend path = auth_backend = airflow.providers.ldap.auth.backend.LDAPAuthBackend [OK]

Hint: Use airflow.providers.ldap.auth.backend.LDAPAuthBackend for LDAP [OK]

Common Mistakes:

• Using incorrect module paths
• Adding extra class names
• Confusing OAuth backend with LDAP

3. Given this snippet in airflow.cfg:

[webserver]
auth_backend = airflow.contrib.auth.backends.oauth_auth

What will happen when a user tries to log in?

medium

A. Airflow will allow login without authentication

B. Airflow will reject all logins because OAuth is not supported

C. Airflow will use LDAP authentication instead

D. Airflow will authenticate the user using OAuth provider settings

Solution

1. Step 1: Identify the configured backend

   The config sets auth_backend to airflow.contrib.auth.backends.oauth_auth, which enables OAuth authentication.

2. Step 2: Understand login behavior

   With OAuth backend, Airflow redirects login to the OAuth provider for user verification.

3. Final Answer:

   Airflow will authenticate the user using OAuth provider settings -> Option D

4. Quick Check:

   OAuth backend means OAuth login [OK]

Hint: OAuth backend means login via OAuth provider [OK]

Common Mistakes:

• Assuming OAuth is unsupported
• Confusing OAuth with LDAP
• Thinking login is disabled

4. You configured LDAP authentication in airflow.cfg but users cannot log in. Which of these is the most likely cause?

medium

A. The Airflow scheduler is not running

B. The DAGs folder is empty

C. The auth_backend setting points to a non-existent module

D. The webserver port is set to 8080

Solution

1. Step 1: Analyze login failure causes

   If users cannot log in after LDAP setup, a common cause is a wrong or missing auth_backend module path.

2. Step 2: Eliminate unrelated causes

   Empty DAGs, scheduler status, or port settings do not affect authentication backend functionality.

3. Final Answer:

   The auth_backend setting points to a non-existent module -> Option C

4. Quick Check:

   Wrong auth_backend module = login failure [OK]

Hint: Check auth_backend module path if login fails [OK]

Common Mistakes:

• Blaming DAGs folder for login issues
• Confusing scheduler status with auth problems
• Thinking port affects authentication

5. You want Airflow to authenticate users via OAuth and also allow admin users to log in with LDAP. Which approach is best to achieve this?

hard

A. Configure a custom authentication backend that combines OAuth and LDAP logic

B. Set auth_backend to LDAP only and ignore OAuth

C. Use OAuth backend and manually add admin users in Airflow database

D. Run two Airflow instances, one with LDAP and one with OAuth

Solution

1. Step 1: Understand multi-backend authentication needs

   Airflow supports one auth_backend at a time, so combining OAuth and LDAP requires custom code.

2. Step 2: Evaluate options

   Configure a custom authentication backend that combines OAuth and LDAP logic suggests creating a custom backend to handle both OAuth and LDAP, which is the correct approach.

3. Step 3: Reject other options

   Setting auth_backend to LDAP only, using OAuth backend and manually adding admin users, or running two Airflow instances do not support both methods simultaneously; the latter is also complex and inefficient.

4. Final Answer:

   Configure a custom authentication backend that combines OAuth and LDAP logic -> Option A

5. Quick Check:

   Multi-auth needs custom backend [OK]

Hint: Combine OAuth and LDAP with custom backend code [OK]

Common Mistakes:

• Trying to set two auth_backends in airflow.cfg
• Ignoring admin user needs
• Running multiple Airflow instances unnecessarily