Authentication basics in Elasticsearch - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the username for basic authentication.

Elasticsearch

client = Elasticsearch(http_auth=([1], 'mypassword'))

Drag options to blanks, or click blank then click option'

A'elastic'

B'password123'

C'user1'

D'admin'

Attempts:

3 left

💡 Hint

Common Mistakes

Putting the password as the first value instead of the username.

Using an incorrect username string.

The username for basic authentication is set as the first element in the http_auth tuple.

2fill in blank

medium

Complete the code to enable SSL verification in the Elasticsearch client.

Elasticsearch

client = Elasticsearch(ssl_show_warn=False, verify_certs=[1])

Drag options to blanks, or click blank then click option'

A'yes'

BNone

CTrue

DFalse

Attempts:

3 left

💡 Hint

Common Mistakes

Using a string instead of a boolean.

Disabling SSL verification by setting it to False.

Setting verify_certs=True enables SSL certificate verification.

3fill in blank

hard

Fix the error in the code to correctly pass the API key for authentication.

Elasticsearch

client = Elasticsearch(api_key=[1])

Drag options to blanks, or click blank then click option'

Ab64encode('api_key')

B'my_api_key'

C('id', 'api_key')

D('id', 'api_key'.encode())

Attempts:

3 left

💡 Hint

Common Mistakes

Passing the API key as a plain string.

Not encoding the API key to bytes.

The api_key parameter expects a tuple of (id, api_key) where the api_key is bytes, so encoding is needed.

4fill in blank

hard

Fill both blanks to create a dictionary with username and password for HTTP basic authentication.

Elasticsearch

auth = {'username': [1], 'password': [2]

Drag options to blanks, or click blank then click option'

A'elastic'

B'mypassword'

C'admin'

D'secret'

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping username and password values.

Using incorrect strings for username or password.

The dictionary keys username and password must be assigned the correct string values for authentication.

5fill in blank

hard

Fill all three blanks to create a secure Elasticsearch client with username, password, and SSL verification enabled.

Elasticsearch

client = Elasticsearch(http_auth=([1], [2]), verify_certs=[3])

Drag options to blanks, or click blank then click option'

A'elastic'

B'mypassword'

CTrue

DFalse

Attempts:

3 left

💡 Hint

Common Mistakes

Disabling SSL verification by setting it to False.

Using incorrect username or password strings.

The http_auth tuple requires username and password strings, and verify_certs should be True to enable SSL verification.

Practice

1. What is the main purpose of authentication in Elasticsearch?

easy

A. To backup the Elasticsearch index

B. To store data securely in the cluster

C. To verify the identity of a user or system before granting access

D. To improve search speed

Solution

1. Step 1: Understand authentication concept

   Authentication is the process of checking who you are before allowing access.

2. Step 2: Match with Elasticsearch context

   Elasticsearch uses authentication to verify user or system identity before access.

3. Final Answer:

   To verify the identity of a user or system before granting access -> Option C

4. Quick Check:

   Authentication = Verify identity [OK]

Hint: Authentication means checking who you are [OK]

Common Mistakes:

• Confusing authentication with data storage
• Thinking authentication speeds up search
• Mixing authentication with backup processes

2. Which of the following is the correct way to call the Elasticsearch API to check your authentication status?

easy

A. GET /_cluster/_health

B. POST /_search/_authenticate

C. PUT /_security/_authenticate

D. GET /_security/_authenticate

Solution

1. Step 1: Identify the correct API endpoint for authentication

   The correct endpoint to verify identity is _security/_authenticate with GET method.

2. Step 2: Check HTTP method correctness

   Authentication check uses GET, not POST or PUT.

3. Final Answer:

   GET /_security/_authenticate -> Option D

4. Quick Check:

   Use GET on _security/_authenticate [OK]

Hint: Use GET method on _security/_authenticate [OK]

Common Mistakes:

• Using POST or PUT instead of GET
• Calling wrong API like _search or _cluster
• Misspelling the endpoint path

3. What will be the result of this curl command if the credentials are correct?

curl -u elastic:changeme -X GET "localhost:9200/_security/_authenticate"

medium

A. An error message saying 'Unauthorized'

B. A JSON response with user details and roles

C. A list of all indices in the cluster

D. A blank response with status 200

Solution

1. Step 1: Understand the curl command

   The command uses basic auth with username 'elastic' and password 'changeme' to call the authenticate API.

2. Step 2: Predict the API response on correct credentials

   If credentials are correct, the API returns JSON with user info and roles, not errors or unrelated data.

3. Final Answer:

   A JSON response with user details and roles -> Option B

4. Quick Check:

   Correct credentials = user info JSON [OK]

Hint: Correct credentials return user info JSON [OK]

Common Mistakes:

• Expecting an error with correct credentials
• Confusing authenticate API with index listing
• Assuming blank response means success

4. You run this command but get an 'Unauthorized' error:

curl -X GET "localhost:9200/_security/_authenticate"

What is the most likely cause?

medium

A. You forgot to include authentication credentials

B. The Elasticsearch cluster is down

C. The API endpoint is incorrect

D. The curl command syntax is invalid

Solution

1. Step 1: Analyze the curl command

   The command calls the authenticate API but does not provide any credentials.

2. Step 2: Understand why 'Unauthorized' occurs

   Without credentials, Elasticsearch denies access, causing 'Unauthorized' error.

3. Final Answer:

   You forgot to include authentication credentials -> Option A

4. Quick Check:

   Missing credentials cause Unauthorized error [OK]

Hint: Always include credentials for secure APIs [OK]

Common Mistakes:

• Assuming cluster is down without checking
• Thinking API endpoint is wrong
• Believing curl syntax is incorrect

5. You want to create an API key for authentication in Elasticsearch using this request:

POST /_security/api_key
{"name": "my-key", "role_descriptors": {"my-role": {"cluster": ["all"]}}}

What is the correct way to authenticate this request?

hard

A. Use basic authentication with a user having the 'manage_api_key' privilege

B. No authentication is needed to create API keys

C. Use the API key itself in the request header

D. Use anonymous access enabled in Elasticsearch

Solution

1. Step 1: Understand API key creation requirements

   Creating API keys requires authentication with a user having 'manage_api_key' privilege.

2. Step 2: Identify correct authentication method

   Basic authentication with such a user is needed; API key or anonymous access won't work for creation.

3. Final Answer:

   Use basic authentication with a user having the 'manage_api_key' privilege -> Option A

4. Quick Check:

   API key creation requires privileged user auth [OK]

Hint: API key creation needs privileged user auth [OK]

Common Mistakes:

• Trying to create API key without authentication
• Using API key before it exists
• Assuming anonymous access allows API key creation