wso2-extensions / identity-governance Goto Github PK

Description:
Cuurently, the WSO2 IS Server facilitates only google recaptcha as a captcha provider in their implementation. This can be a problem in instances where google services are blocked etc. Also, with the current implementation only google recaptcha can be used and it cannot be changed to any provider based on a customer requirement. This can be improved by allowing the customers to define their own use cases and assigning captcha providers accordingly.

Suggested Labels:
improvements

Suggested Assignees:

Affected Product Version:

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

Description:
All the user recovery data belongs to a tenant should be deleted in the tenant deletion process.

Related Issues:
wso2/carbon-multitenancy#146

Description:
Password history data of the users should be deleted in the tenant deletion process.

Related Issues:
wso2/carbon-multitenancy#146

Hello, I wonder, what is the difference between this project and https://github.com/wso2/carbon-identity-mgt?

Description:
a minor grammatical issue in the GUI: "notification internally management" should be "internal notification management" or "internally managed notifications"

this is found in at least 8 code locations, also including the account-lock plugin:
https://github.com/search?utf8=%E2%9C%93&q=org%3Awso2-extensions+%22internally+management%22&type=Code

Suggested Labels:
Type/UX

Suggested Assignees:

Affected Product Version:
IS 5.4.0 default distribution

OS, DB, other environment details and versions:
using Debian 9 with LXDE in VirtualBox

Steps to reproduce:

• install WSO2 IS 5.4.0
• open the admin console, go to "Main" -> "Identity" -> "Identity Providers" -> "Resident" -> "Account Management Policies" -> "Account Recovery"
• see checkbox option for "Enable Notification Internally Management"

Related Issues:
wso2-extensions/identity-event-handler-account-lock#43