This is a consolidated repo of Workflow Guides for F5 products: BigIP and BigIP Next, covering select use-cases with automation and their manual step equivalents. Use the guides and associated automation scripts to become familiar with the use-cases outlined in the table below, and with the automation code provided for these use-cases (Ansible, Terraform, etc.)
NOTE: To learn about each use case check the DevCentral article link provided in the table below.
Note: Next CM API specification can be found over this link F5® BIG-IP® Next Central Manager API Specifications.
| DevCentral Overview Articles | Use Case / Workflow Guides (SaaS Console, Automation) |
|---|---|
| Introducing Next Access Alongside Our Trusted APM | N/A |
| SAML Federation made easier | Microsoft EntraID (SAML IdP) with Kerberos SSO |
| Integration with Okta (SAML IdP) | |
| Integration with Okta (SAML IdP) with HTTP Connector providing risk rating | |
| [Multiple IdPs based on matching criteria] | |
| VPN Use cases | Edge client with Machine certificate |
| Machine Tunnel with Machine certificate |
| DevCentral Overview Articles | Use Case / Workflow Guides (SaaS Console, Automation) |
|---|---|
| Migrate Apps with WAF Policy from BIG-IP TMOS to BIG-IP Next (Coming Soon) | Manual Steps and Automation (Ansible) for BIG-IP TMOS to Next Migration |
| Deploy and Protect Apps on BIG-IP Next (Coming Soon) | Manual Steps and Automation (Terraform) for Deploying a New App with WAF Policy |
| Next WAF Operations (Coming Soon) | Manual Steps and Automation (Ansible) for WAF Signature Updates & Operations |
- Access the README for the target Workflow Guides use-case(s) from the tables above.
- Follow the steps in the README and follow Manual and/or Automated workflows
For support, please open a GitHub issue. Note, the code in this repository is community supported and is not supported by F5, Inc.
Please refer to the F5 DevCentral Community Code of Conduct.
Copyright 2014-2023 F5 Networks Inc.
Before you start contributing to any project sponsored by F5 Networks, Inc. (F5) on GitHub, you will need to sign a Contributor License Agreement (CLA).
If you are signing as an individual, we recommend that you talk to your employer (if applicable) before signing the CLA since some employment agreements may have restrictions on your contributions to other projects. Otherwise by submitting a CLA you represent that you are legally entitled to grant the licenses recited therein.
If your employer has rights to intellectual property that you create, such as your contributions, you represent that you have received permission to make contributions on behalf of that employer, that your employer has waived such rights for your contributions, or that your employer has executed a separate CLA with F5.
If you are signing on behalf of a company, you represent that you are legally entitled to grant the license recited therein. You represent further that each employee of the entity that submits contributions is authorized to submit such contributions on behalf of the entity pursuant to the CLA.