<commit_before>LAB 1.2 - API Authentication
=============================

Overview
---------

The iControl REST API requires initial authentication in the form of a username/password.  After authentication is successful, a token can be used to make subsequent API calls.

Preface
--------

Prior to performing this lab, the Postman environemnt should valided.  The **{{big_ip_a_mgmt}}** variable should be set to the host name of the BIG-IP's management GUI.  In this case, the Postman environment variable should already be set ```bigipa.f5demo.com``` for this lab.  

Prior to perforing any of the below steps, ensure that you can log into the BIG-IP with Chrome after accepting the invalid certificate.  Postman relies on the Chrome certificate store and if the self-signed cert has not been accepted via Chrome, this extension will not work properly.

#. Launch Chrome and click on the BIG-IP_A bookmar in the tool bar.

|image-1|

#. A certificate warning should be displayed.  Click on the ```ADVANCED``` link in the lower left-hand side of the warning message.

|image-2|

#. Accept the invalide certificate by clicking on the ```Proceed to bigipa.f5demo.com (unsafe)``` link.

|image-3|

#. The BIG-IP management GUI should now be displayed.

|image-4|

#. Log into the BIG-IP using the default user name and password.

.. warning:: If you do not first log into the BIG-IP and accept the invalid certificate with Chrome, Postman will state ```could not get any response``` when sending a request to the BIG-IP.

|image-5|

Lab Specific Instructions
--------------------------

Follow the **Lab 1.2 - API Authentication** steps in order found in the Postman collection to complete this portion of the lab.  The requests and responses have been included below for referance.

In this lab, the basic authenication value is the base64-encoding of the BIG-IPs default username and password **admin:admin**.

Once successfully authenticated, the BIG-IP response will respond with an authentication token that should be copied and placed into the **{{big_ip_a_auth_token}}** Postman environemnt variable.

.. attention:: Some response content has been removed for brevity.

1. HTTP BASIC Authentication
-----------------------------

**Request**

:: <commit_msg>Mostly typos<commit_after>LAB 1.2 - API Authentication
=============================

Overview
---------

The iControl REST API requires initial authentication in the form of a username/password.  After authentication is successful, a token can be used to make subsequent API calls.

Preface
--------

Prior to performing this lab, the Postman environemnt should be validated.  The **{{big_ip_a_mgmt}}** variable should be set to the host name of the BIG-IP's management GUI.  In this case, the Postman environment variable should already be set ```bigipa.f5demo.com``` for this lab.  

Prior to perforing any of the below steps, ensure that you can log into the BIG-IP with Chrome after accepting the invalid certificate.  Postman relies on the Chrome certificate store and if the self-signed cert has not been accepted via Chrome, this extension will not work properly.

#. Launch Chrome and click on the "BIG-IP A GUI" bookmark on the tool bar.

|image-1|

#. A certificate warning should be displayed.  Click on the ```ADVANCED``` link in the lower left-hand side of the warning message.

|image-2|

#. Accept the invalide certificate by clicking on the ```Proceed to bigipa.f5demo.com (unsafe)``` link.

|image-3|

#. The BIG-IP management GUI should now be displayed.

|image-4|

#. Log into the BIG-IP using the default user name and password (<PASSWORD>).

.. warning:: If you do not first log into the BIG-IP and accept the invalid certificate with Chrome, Postman will state ```could not get any response``` when sending a request to the BIG-IP.

|image-5|

Lab Specific Instructions
--------------------------

Follow the **Lab 1.2 - API Authentication** steps in order found in the Postman collection to complete this portion of the lab.  The requests and responses have been included below for referance.

In this lab, the basic authenication value is the base64-encoding of the BIG-IPs default username and password **<PASSWORD>**.

Once successfully authenticated, the BIG-IP response will respond with an authentication token that should be copied and placed into the **{{big_ip_a_auth_token}}** Postman environemnt variable.

.. attention:: Some response content has been removed for brevity.

1. HTTP BASIC Authentication
-----------------------------

**Request**

:: 
{'fraction_non_alphanumeric': 0.10876730388925511, 'fraction_numerical': 0.0061524939573720065, 'mean_word_length': 3.6639344262295084, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3601250', 'n_tokens_mistral': 1221, 'n_tokens_neox': 1155, 'n_words': 627}