Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix the issue https://github.com/wso2/product-is/issues/21192 #2587

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

DMHP
Copy link
Contributor

@DMHP DMHP commented Oct 7, 2024

Proposed changes in this pull request

Fix Inconsistent Error Responses in Device Flow

When should this PR be merged

Immediately

Follow-up actions

  • Add an integration test to cover this flow
  • Add unit tests

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.

Copy link

codecov bot commented Oct 7, 2024

Codecov Report

Attention: Patch coverage is 46.66667% with 24 lines in your changes missing coverage. Please review.

Project coverage is 53.88%. Comparing base (61494ba) to head (0e81592).
Report is 70 commits behind head on master.

Files with missing lines Patch % Lines
.../identity/oauth2/device/dao/DeviceFlowDAOImpl.java 0.00% 12 Missing ⚠️
.../identity/oauth2/device/grant/DeviceFlowGrant.java 63.63% 9 Missing and 3 partials ⚠️
Additional details and impacted files
@@              Coverage Diff              @@
##             master    #2587       +/-   ##
=============================================
+ Coverage     41.99%   53.88%   +11.89%     
- Complexity     6005     8504     +2499     
=============================================
  Files           601      632       +31     
  Lines         44553    50603     +6050     
  Branches       7010     8533     +1523     
=============================================
+ Hits          18710    27268     +8558     
+ Misses        22382    19222     -3160     
- Partials       3461     4113      +652     
Flag Coverage Δ
unit 38.08% <46.66%> (?)

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.

@@ -53,6 +54,8 @@
import java.util.TimeZone;
import java.util.UUID;

import static org.wso2.carbon.identity.oauth2.device.constants.Constants.SLOW_DOWN;
Copy link
Contributor

Choose a reason for hiding this comment

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

We already imported

org.wso2.carbon.identity.oauth2.device.constants.Constants

in line 36.

We don't need to import this static constant, we can directly use

Constants.SLOW_DOWN

deviceFlowDO.setDeviceCode(deviceCode);
setLastPollTime(deviceCode);
} catch (IdentityOAuth2Exception e) {
deviceStatus = e.getMessage();
Copy link
Contributor

Choose a reason for hiding this comment

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

we don't need this line right?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Contributor

Choose a reason for hiding this comment

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

this catch block don't get execute after line 76, cause handleInvalidRequests method throws identityOAuthException anyway.

Thumimku
Thumimku previously approved these changes Oct 11, 2024
Copy link
Contributor

@Thumimku Thumimku left a comment

Choose a reason for hiding this comment

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

can improve the code with said comments, LGTM. Let's run integration tests for safe side.

Thumimku
Thumimku previously approved these changes Oct 11, 2024
@DMHP
Copy link
Contributor Author

DMHP commented Oct 14, 2024

This PR contains a basic set of unit tests to cover the flow I added. However, this flow requires comprehensive unit tests to cover the whole flow. I will work on improving those.

@@ -47,14 +61,19 @@ public class DeviceFlowGrantTest {
private Timestamp newTime = new Timestamp(date.getTime());
private DeviceFlowDO deviceFlowDO1 = new DeviceFlowDO();
private DeviceFlowDO deviceFlowDO2 = new DeviceFlowDO();
private DeviceFlowGrant deviceFlowGrant;
private OAuthTokenReqMessageContext oAuthTokenReqMessageContext;
private DeviceFlowDO deviceFlowDO3;
Copy link
Contributor

Choose a reason for hiding this comment

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

cant we move near to other DOs

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.

3 participants