Systems | Development | Analytics | API | Testing

In this episode, we will be discussing all about account locking in the WSO2 Identity Server. There are two main types of Account Locking in the IS which are Admin-Initiated Account Locking and Account Locking due to Failed Login Attempts. In this session we will be discussing these types in depth and how you can enforce them.

In today's episode, we will discuss how you can manage your user profiles with SCIM by using WSO2 Identity Server as a SCIM service provider in just 15mins. The System for Cross-domain Identity Management (SCIM) specification is designed to manage user identity in cloud-based applications and services in a standardized way to enable interoperability, security, and scalability.

In this episode, we will be demonstrating how to plug in your existing user base to the WSO2 Identity Server in just 15mins.

As the organization adapts the process to the needs of the stakeholders, the delivery process becomes faster and more efficient..

Consumers see the world as all digital with no divide. As a result, whether those consumers are young, old, digitally savvy, or technophobes; organizations are going to have to find a way to ‘deliver better customer interactions’ than their competitors if they are to acquire and retain them. Customer Identity and Access Management (CIAM) can be defined as “A customer-focused IAM discipline that facilitates leveraging identity data with business data to catalyze business growth”.

In Choreo Connect 1.1.0 release, mock APIs are supported considering the API definition file. Users can define mock responses in Open API Specification 3 (OAS 3) or using Swagger definition. With the latest WSO2 API Manager 4.1.0 release, the relevant endpoint type for this API type is Mock Implementation Endpoint type. These APIs are manipulated under the pre-released API lifecycle state. With Choreo Connect API definition based mock implementations, you can define default responses, HTTP status code based responses, status code based preferred response retrievals.

Open policy agent (OPA) enables you to write security and compliance policies as code, or call any external policies using the OPA standard. WSO2 API manager uses this capability to offload policy decisions of API gateway requests to this policy engine. By decoupling the policy enforcement from evaluation, API policymakers now have the opportunity to write dynamic and reusable policies for ever-changing requirements. You can then reuse an OPA policy like any other policy in the API Manager by graphically dragging and dropping it into a policy pipeline. This video explains how it works and gives a demo.

In this session of #IdentityIn15, we will be demonstrating how you can secure your Express applications with OIDC authentication using Asgardeo Express SDK.