Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fixes #23

Merged
merged 1 commit into from
Sep 6, 2024
Merged

fixes #23

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 0 additions & 5 deletions docs/class1/module1/lab3.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,11 +8,6 @@ Test Connectivity to the Application

2. In a new Firefox browser window type the following URL: https://signed.example.com

You may get a security warning **Your Connection is Not Private**, this is because we're using a self-signed certificate. It is safe to proceed.

.. image:: images/lab4-warn.png
:width: 600 px

3. When prompted for Okta authentication enter the following username/password: user1/user1

.. image:: images/lab4-logon.png
Expand Down
1 change: 0 additions & 1 deletion docs/class1/module2/module2.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,6 @@ In this lab we will explore how to setup SAML authentication with EntraID as SAM
**Learning Objectives:**

- Create DNS resolver.
- Upload Certificate to the CM.
- Create Policy via Visual Policy Designer (VPD).
- Include SSO in the configurations.
- Assign Flows and rules to the policy.
Expand Down
Binary file added docs/class2/module1/images/lab1-advresource.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
14 changes: 9 additions & 5 deletions docs/class2/module1/lab1.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,13 +60,14 @@ In the **General Properties** screen set the following parameters, for the rest

* Click **Start Creating**, and create a **Network Access** resource. Configure as below

* Change to split tunneling
* Change to ``split tunneling``, with ``address space`` 10.1.20.0/24


.. image:: images/lab1-networkaccess.png
:width: 800 px

* Give a name to the lease pool : leasepool1
* DNS/Host, set IPv4 primary Name Server to : 10.1.20.6
* Continue and give a name to the lease pool : leasepool1
* Continue to DNS/Host, set IPv4 primary Name Server to : 10.1.20.6
* Click **continue** till end and **Finish**

* Click **Create** and create a new resource type **Webtop**
Expand Down Expand Up @@ -153,6 +154,9 @@ The result should look like the following screen shot.

21. Add a new rule **Advanced Resource Assign** next to the Successful branch, **edit** it, and add your **webtop** and **network access** resources.

.. image:: images/lab1-advresource.png
:width: 600 px

* Do not select any context, keep it empty
* Add your webtop and Network Access

Expand All @@ -165,9 +169,9 @@ The result should look like the following screen shot.
* Click **finish** and save your Advanced Resource Assign rule (by clicking to **continue**).


22. Click on the **Collapse** button to close the **Rules and Flow** box so you’re back to the main VPD. S
1. Click on the **Collapse** button to close the **Rules and Flow** box so you’re back to the main VPD. S

23. On the **Allow** branch, change the ending to **Allow**.
2. On the **Allow** branch, change the ending to **Allow**.

.. image:: images/lab1-final-allow.png
:width: 600 px
Expand Down
14 changes: 7 additions & 7 deletions docs/class2/module1/lab2.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,18 +78,18 @@ Creating an application and assign an Access policy to the application
.. image:: images/lab2-revdeploy.png
:width: 600 px

1. In the **Deploy** screen, this is where you define which BIG-IP Next instance to deploy the application. Click on **Start Adding** to select a BIG-IP Next Instance.
16. In the **Deploy** screen, this is where you define which BIG-IP Next instance to deploy the application. Click on **Start Adding** to select a BIG-IP Next Instance.

18. In the drop down box, select *big-ip-next-03.example.com*, then click on **Add to List** button.
17. In the drop down box, select *big-ip-next-03.example.com*, then click on **Add to List** button.

19. In the **Virtual Address:** box type: **10.1.10.160** to associate with the virutal server vs-vpn.
18. In the **Virtual Address:** box type: **10.1.10.160** to associate with the virutal server vs-vpn.

20. You must configure your Lease Pool for this Next instance. To do so, click on **Configure** (the one next to the ...Actions button)
19. You must configure your Lease Pool for this Next instance. To do so, click on **Configure** (the one next to the ...Actions button)

.. image:: images/lab2-clickconfigure.png
:width: 600 px

21. Click on your Per-Session policy and set the Lease Pool range to ``10.1.20.230`` to ``10.1.20.235``
20. Click on your Per-Session policy and set the Lease Pool range to ``10.1.20.230`` to ``10.1.20.235``

.. image:: images/lab2-clicksslvpn.png
:width: 600 px
Expand All @@ -100,9 +100,9 @@ Creating an application and assign an Access policy to the application
* Click **Save** and **Finish**


22. Now you’re ready to Deploy your application. Click on **Deploy Changes** at the bottom right-hand corner.
21. Now you’re ready to Deploy your application. Click on **Deploy Changes** at the bottom right-hand corner.

23. Confirm in the pop-up window that you’re deploy to *big-ip-next-03.example.com* instance.
22. Confirm in the pop-up window that you’re deploy to *big-ip-next-03.example.com* instance.

* Click on **Yes, Deploy**

Expand Down
Loading