Systems | Development | Analytics | API | Testing

Latest Videos

Enable Tenant Configuration menu in Admin portal

WSO2 API Manager 4.1 offers a new and enhanced user interface called Advanced Configurations through Admin Portal for administrative users to easily configure feature-related central configurations. In previous WSO2 API Manager versions the same configuration, which was previously known as Tenant Configuration, was accessible through the management console using the registry. Now with the introduction of the Advanced Configuration user interface with schema validation capabilities, all the administrative tasks related to API Manager features can be done through the Admin Portal.

Building a Next-Gen API Platform with the All-New Choreo Connect Microgateway, WSO2 Webinar

Microservices have become the de facto standard in modern application architecture. Modern application workloads are spread among several groups of microservices, cloud services, and legacy services. Kubernetes has become the industry standard for deploying microservices, with service meshes allowing developers to isolate and control service-to-service connections. Choreo Connect is an API microgateway that is cloud-native, open-source, and developer-focused. It offers first-rate Kubernetes support while supporting a variety of API management quality of services (QoS), such as message security rate-limiting, observability, and message mediation.

Getting the Developer Community Involved (Scenario 5) - WSO2 API Manager 4.0 Use Case - Part 6

This tutorial is part of a series and can also be used as a standalone tutorial on how to get the developer community involved. For more details on the scenario and general prerequisites, please watch the previous videos on this series.

What the heck is DPoP? | IAM Community Meetups - 2022

An Application-level proof-of-possession protections for access and refresh tokens. DPoP (Demonstrating-Proof-of-Possession) is an additional security mechanism for the token generation which overcomes the issue of bearer token which will not validate between who is requested token and who is actually using the token for the access of a particular resource. In DPoP, this will be avoided by validating the client who requested the token is the one who is actually using the token using the Signed JWT tokens known as DPoP Proof.