Systems | Development | Analytics | API | Testing

Re-issue Existing Password Recovery Confirmation Code in Followed Recovery or Resend Requests

Photo by Micah Williams on Unsplash This article discusses a new feature which will be released for the public distribution of WSO2 Identity Server 5.12.0. This feature was developed to overcome the following scenario: You can refer to the following diagram for a deeper understanding of the above flow. This scenario can be experienced by anyone. As such, we introduced a new way to handle this scenario (as shown below) for the notification based password recovery flow.

How to Plug an Existing User Store into WSO2 Identity Server?

Are you someone who already has a legacy system in place and wants to migrate to a modern authentication system with Identity and Access Management (IAM) features? The first thing you need to consider is how you can use the existing legacy user store with this new system. Keep in mind that if the legacy user store uses an old security mechanism to store your data, we would recommend that you migrate to the WSO2 JDBC user store format or Active Directory (AD).

Proof of possession for OAuth2 tokens(DPoP) with WSO2 Identity Server #Identityin15

In today's episode, we will discuss how you can secure OAuth2 Tokens with DPoP using the WSO2 Identity Server. 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. The following is the outline for today's session.