Skip to content

Conversation

@PasinduYeshan
Copy link
Contributor

Proposed changes in this pull request

[List all changes you want to add here. If you fixed an issue, please
add a reference to that issue as well.]

When should this PR be merged

[Please describe any preconditions that need to be addressed before we
can merge this pull request.]

Follow up actions

[List any possible follow-up actions here; for instance, testing data
migrations, software that we need to install on staging and production
environments.]

Checklist (for reviewing)

General

  • Is this PR explained thoroughly? All code changes must be accounted for in the PR description.
  • Is the PR labeled correctly?

Functionality

  • Are all requirements met? Compare implemented functionality with the requirements specification.
  • Does the UI work as expected? There should be no Javascript errors in the console; all resources should load. There should be no unexpected errors. Deliberately try to break the feature to find out if there are corner cases that are not handled.

Code

  • Do you fully understand the introduced changes to the code? If not ask for clarification, it might uncover ways to solve a problem in a more elegant and efficient way.
  • Does the PR introduce any inefficient database requests? Use the debug server to check for duplicate requests.
  • Are all necessary strings marked for translation? All strings that are exposed to users via the UI must be marked for translation.

Tests

  • Are there sufficient test cases? Ensure that all components are tested individually; models, forms, and serializers should be tested in isolation even if a test for a view covers these components.
  • If this is a bug fix, are tests for the issue in place? There must be a test case for the bug to ensure the issue won’t regress. Make sure that the tests break without the new code to fix the issue.
  • If this is a new feature or a significant change to an existing feature? has the manual testing spreadsheet been updated with instructions for manual testing?

Security

  • Confirm this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets.
  • Are all UI and API inputs run through forms or serializers?
  • Are all external inputs validated and sanitized appropriately?
  • Does all branching logic have a default case?
  • Does this solution handle outliers and edge cases gracefully?
  • Are all external communications secured and restricted to SSL?

Documentation

  • Are changes to the UI documented in the platform docs? If this PR introduces new platform site functionality or changes existing ones, the changes should be documented.
  • Are changes to the API documented in the API docs? If this PR introduces new API functionality or changes existing ones, the changes must be documented.
  • Are reusable components documented? If this PR introduces components that are relevant to other developers (for instance a mixin for a view or a generic form) they should be documented in the Wiki.

Comment on lines 122 to +123
boolean supportMultipleMobileNumbers =
Utils.isMultiEmailsAndMobileNumbersPerUserEnabled(user.getTenantDomain(), user.getUserStoreDomain());
Utils.isMultiMobileNumbersPerUserEnabled(user.getTenantDomain(), user.getUserStoreDomain());

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Log Improvement Suggestion No: 1

Suggested change
boolean supportMultipleMobileNumbers =
Utils.isMultiEmailsAndMobileNumbersPerUserEnabled(user.getTenantDomain(), user.getUserStoreDomain());
Utils.isMultiMobileNumbersPerUserEnabled(user.getTenantDomain(), user.getUserStoreDomain());
boolean supportMultipleMobileNumbers =
Utils.isMultiMobileNumbersPerUserEnabled(user.getTenantDomain(), user.getUserStoreDomain());
if (log.isDebugEnabled()) {
log.debug("Multiple mobile numbers support is " + (supportMultipleMobileNumbers ? "enabled" : "disabled") + " for user: " + user.getLoggableUserId());
}

Comment on lines 344 to +345
boolean supportMultipleMobileNumbers =
Utils.isMultiEmailsAndMobileNumbersPerUserEnabled(user.getTenantDomain(), user.getUserStoreDomain());
Utils.isMultiMobileNumbersPerUserEnabled(user.getTenantDomain(), user.getUserStoreDomain());

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Log Improvement Suggestion No: 2

Suggested change
boolean supportMultipleMobileNumbers =
Utils.isMultiEmailsAndMobileNumbersPerUserEnabled(user.getTenantDomain(), user.getUserStoreDomain());
Utils.isMultiMobileNumbersPerUserEnabled(user.getTenantDomain(), user.getUserStoreDomain());
boolean supportMultipleMobileNumbers =
Utils.isMultiMobileNumbersPerUserEnabled(user.getTenantDomain(), user.getUserStoreDomain());
if (log.isDebugEnabled()) {
log.debug("Checking multiple mobile numbers support for claim update. Support enabled: " + supportMultipleMobileNumbers);
}

Comment on lines 124 to +125
boolean supportMultipleEmails =
Utils.isMultiEmailsAndMobileNumbersPerUserEnabled(user.getTenantDomain(), user.getUserStoreDomain());
Utils.isMultiEmailAddressesPerUserEnabled(user.getTenantDomain(), user.getUserStoreDomain());

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Log Improvement Suggestion No: 3

Suggested change
boolean supportMultipleEmails =
Utils.isMultiEmailsAndMobileNumbersPerUserEnabled(user.getTenantDomain(), user.getUserStoreDomain());
Utils.isMultiEmailAddressesPerUserEnabled(user.getTenantDomain(), user.getUserStoreDomain());
boolean supportMultipleEmails =
Utils.isMultiEmailAddressesPerUserEnabled(user.getTenantDomain(), user.getUserStoreDomain());
if (log.isDebugEnabled()) {
log.debug("Multiple email addresses support: " + supportMultipleEmails + " for user: " + user.getLoggableUserId());
}

Comment on lines 554 to +555
boolean supportMultipleEmails =
Utils.isMultiEmailsAndMobileNumbersPerUserEnabled(user.getTenantDomain(), user.getUserStoreDomain());
Utils.isMultiEmailAddressesPerUserEnabled(user.getTenantDomain(), user.getUserStoreDomain());

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Log Improvement Suggestion No: 4

Suggested change
boolean supportMultipleEmails =
Utils.isMultiEmailsAndMobileNumbersPerUserEnabled(user.getTenantDomain(), user.getUserStoreDomain());
Utils.isMultiEmailAddressesPerUserEnabled(user.getTenantDomain(), user.getUserStoreDomain());
boolean supportMultipleEmails =
Utils.isMultiEmailAddressesPerUserEnabled(user.getTenantDomain(), user.getUserStoreDomain());
if (log.isDebugEnabled()) {
log.debug("Checking multiple email support for email update. Support enabled: " + supportMultipleEmails);
}

IdentityGovernanceService identityGovernanceService = IdentityRecoveryServiceDataHolder.getInstance()
.getIdentityGovernanceService();
connectorConfigs = identityGovernanceService.getConfiguration(new String[]{key,}, tenantDomain);
connectorConfigs = identityGovernanceService.getConfiguration(new String[]{key}, tenantDomain);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Log Improvement Suggestion No: 5

Suggested change
connectorConfigs = identityGovernanceService.getConfiguration(new String[]{key}, tenantDomain);
connectorConfigs = identityGovernanceService.getConfiguration(new String[]{key}, tenantDomain);
if (log.isDebugEnabled()) {
log.debug("Retrieved sign up configuration for key: " + key + " in tenant: " + tenantDomain);
}

Comment on lines +1564 to +1566
isEmailVerificationOnUpdateEnabled = isEmailVerificationOnUpdateEnabled(tenantDomain);
} catch (IdentityEventException e) {
log.error("Error while retrieving email verification on update config.", e);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Log Improvement Suggestion No: 6

Suggested change
isEmailVerificationOnUpdateEnabled = isEmailVerificationOnUpdateEnabled(tenantDomain);
} catch (IdentityEventException e) {
log.error("Error while retrieving email verification on update config.", e);
} catch (IdentityEventException e) {
log.error("Error while retrieving email verification on update config for tenant: " + tenantDomain);
return false;

Copy link

@wso2-engineering wso2-engineering bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AI Agent Log Improvement Checklist

⚠️ Warning: AI-Generated Review Comments

  • The log-related comments and suggestions in this review were generated by an AI tool to assist with identifying potential improvements. Purpose of reviewing the code for log improvements is to improve the troubleshooting capabilities of our products.
  • Please make sure to manually review and validate all suggestions before applying any changes. Not every code suggestion would make sense or add value to our purpose. Therefore, you have the freedom to decide which of the suggestions are helpful.

✅ Before merging this pull request:

  • Review all AI-generated comments for accuracy and relevance.
  • Complete and verify the table below. We need your feedback to measure the accuracy of these suggestions and the value they add. If you are rejecting a certain code suggestion, please mention the reason briefly in the suggestion for us to capture it.
Comment Accepted (Y/N) Reason
#### Log Improvement Suggestion No: 1
#### Log Improvement Suggestion No: 2
#### Log Improvement Suggestion No: 3
#### Log Improvement Suggestion No: 4
#### Log Improvement Suggestion No: 5
#### Log Improvement Suggestion No: 6

@codecov
Copy link

codecov bot commented Nov 19, 2025

Codecov Report

❌ Patch coverage is 74.00000% with 13 lines in your changes missing coverage. Please review.
✅ Project coverage is 54.36%. Comparing base (8d798f9) to head (53242c5).
⚠️ Report is 5 commits behind head on master.

Files with missing lines Patch % Lines
.../org/wso2/carbon/identity/recovery/util/Utils.java 71.73% 9 Missing and 4 partials ⚠️
Additional details and impacted files
@@             Coverage Diff              @@
##             master    #1078      +/-   ##
============================================
+ Coverage     54.34%   54.36%   +0.01%     
- Complexity     3134     3145      +11     
============================================
  Files           316      316              
  Lines         21485    21524      +39     
  Branches       4103     4108       +5     
============================================
+ Hits          11677    11701      +24     
- Misses         8318     8329      +11     
- Partials       1490     1494       +4     
Flag Coverage Δ
unit 45.52% <74.00%> (+0.03%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant