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

chore: fix sonar issues #3789

Open
wants to merge 6 commits into
base: v3.x.x
Choose a base branch
from
Open

Conversation

richard-salac
Copy link
Contributor

@richard-salac richard-salac commented Sep 20, 2024

Description

Resolve sonar issues

Type of change

Please delete options that are not relevant.

  • fix: Bug fix (non-breaking change which fixes an issue)
  • feat: New feature (non-breaking change which adds functionality)
  • docs: Change in a documentation
  • refactor: Refactor the code
  • chore: Chore, repository cleanup, updates the dependencies.
  • BREAKING CHANGE or !: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • My code follows the style guidelines of this project
  • PR title conforms to commit message guideline ## Commit Message Structure Guideline
  • I have commented my code, particularly in hard-to-understand areas. In JS I did provide JSDoc
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • The java tests in the area I was working on leverage @nested annotations
  • Any dependent changes have been merged and published in downstream modules

For more details about how should the code look like read the Contributing guideline

…kPeriod=true&issueStatuses=OPEN%2CCONFIRMED&branch=v3.x.x&id=zowe_api-layer&open=AZG8RKZMaDaTTh7MLIqJ&tab=code

Signed-off-by: Richard Salac <richard.salac@broadcom.com>
Signed-off-by: Richard Salac <richard.salac@broadcom.com>
@github-actions github-actions bot added the Sensitive Sensitive change that requires peer review label Sep 20, 2024
…kPeriod=true&issueStatuses=OPEN%2CCONFIRMED&branch=v3.x.x&id=zowe_api-layer&open=AZG8RK7RaDaTTh7MLItk

Signed-off-by: Richard Salac <richard.salac@broadcom.com>
…kPeriod=true&issueStatuses=OPEN%2CCONFIRMED&branch=v3.x.x&id=zowe_api-layer&open=AZG8RKvGaDaTTh7MLIsc

Signed-off-by: Richard Salac <richard.salac@broadcom.com>
…kPeriod=true&issueStatuses=OPEN%2CCONFIRMED&branch=v3.x.x&id=zowe_api-layer&open=AZG8RKyvaDaTTh7MLIsj

Signed-off-by: Richard Salac <richard.salac@broadcom.com>
Signed-off-by: Richard Salac <richard.salac@broadcom.com>
@pull-request-size pull-request-size bot added size/L and removed size/S labels Sep 20, 2024
@richard-salac richard-salac self-assigned this Sep 20, 2024
Copy link

sonarcloud bot commented Sep 20, 2024

ArrayList<String> result = new ArrayList<>();

String ssoCookie = getAuthenticationCookie(passedAuthenticationToken);

HttpHeaders headersSSO = new HttpHeaders();
Copy link
Contributor

Choose a reason for hiding this comment

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

We cannot remove JWT from the calls. It is necessary to obtain it from the Authentication object (security context). And in the case, JWT is not accessible there (ie. access with x509), obtain a new token.

@@ -186,8 +145,8 @@ private List<String> fromResponseReturnFoundProblems(ResponseEntity<String> resp
result.add("Documented endpoint at " + currentEndpoint.getUrl() + " could not be located, attempting to call it through gateway gives the ZWEAM104E error");
}

if (attemptWithSSO && responseBody != null && (response.getStatusCode() == HttpStatus.FORBIDDEN || response.getStatusCode() == HttpStatus.UNAUTHORIZED)) {
result.add(method + " request to documented endpoint at " + currentEndpoint.getUrl() + " responded with status code " + response.getStatusCode().value() + ", despite being called with the SSO authorization");
Copy link
Contributor

Choose a reason for hiding this comment

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

Once user is authenticated the SSO message is still valid I guess

* @return List of problems
*/
public List<String> testEndpointsByCalling(Set<Endpoint> endpoints, String passedAuthenticationToken) {
ArrayList<String> result = new ArrayList<>(checkEndpointsNoSSO(endpoints));
Copy link
Contributor

Choose a reason for hiding this comment

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

It maybe make sense to call each endpoint twice (with and without JWT)

@@ -106,7 +105,7 @@ void checkValidJson() {
void whenServiceIdTooLong_thenNonconformant() {
when(messageService.createMessage(NON_CONFORMANT_KEY, "ThisWillBeRemoved")).thenReturn(NON_CONFORMANT_MESSAGE);
String testString = "qwertyuiopqwertyuiopqwertyuiopqwertyuiopqwertyuiopqwertyuiopqwertyuiop";
result = validateAPIController.checkConformance(testString, "dummy");
Copy link
Contributor

Choose a reason for hiding this comment

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

There is no test with credentials?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Sensitive Sensitive change that requires peer review size/L
Projects
Development

Successfully merging this pull request may close these issues.

2 participants