This lab demonstrates the use case for securing a Open Banking transaction initiated by a PSU (Payment Service User) by logging into the TPP (Third Party App).

This is a Cisco Identity Service Engine (ISE) version 2.6 lab migrating to version ISE 3.1. In this lab, we will show how to migrate an ISE server to version 3.1. After migrating, we will step through how to setup basic policy including: Authentication, Authorization and MAB. This setup will show some of the differences between ISE 2.X UI and the new 3.X UI as well as make note of best practices, and how to avoid common pitfalls with this migration.

Welcome to WWT's F5 APM Identify and Access management sandbox. This capability is a fully functioning sandbox that demonstrates how F5 APM can be used to achieve various levels of access control within an enterprise, such as Single Sign-On and VPN.

The Aruba Training Lab provides you with two ClearPass servers, one wireless LAN Controller, an 1 Aruba wireless access point, wired and wireless test clients as well as the support servers you need for training. After completing this lab, you will have all the information needed to support a hands on deployment of Aruba Clearpass.

The purpose of this lab is to demo how NGINX Controller API Management Module and NGINX App Protect can secure the OAuth Authorization Code flow, which is core to Open Banking specifications. The NGINX App Protect will be deployed as an Ingress Controller for Kubernetes and will provide both negative and positive security by ingesting the OpenAPI declaration file. The NGINX API Gateway will be controlled by NGINX Controller, will publish the application API based on the same OpenAPI declaration file, will provide JWT authentication and authorization and enforce rate limiting. The deployment and configuration of these elements will be performed automatically through a CI/CD pipeline. ELK dashboards will be used for visualization purposes and, lastly, a DAST tool will also be run as part of the CI/CD pipeline. BIG-IP APM is deployed as both Authorization Server with OpenID Connect support and as OAuth Client, in separate instances.