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

Feature: JDK 17 Upgrade Support Series - Policy Decision Point #354

Closed
6 tasks done
cwoods-cpointe opened this issue Sep 20, 2024 · 2 comments · Fixed by #375
Closed
6 tasks done

Feature: JDK 17 Upgrade Support Series - Policy Decision Point #354

cwoods-cpointe opened this issue Sep 20, 2024 · 2 comments · Fixed by #375
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@cwoods-cpointe
Copy link
Contributor

cwoods-cpointe commented Sep 20, 2024

Description

In #133 we modified the build-parent to use JDK 17. When building aiSSEMBLE with the updated build-parent, some modules do not build successfully. This is a series of ticket to fix broken modules. This issue will focus on the policy decision point functionality

DOD

  • Modify the foundation-security and extensions-security modules to build successful
  • Deploy the PDP service through Helm
  • Verify the PDP service is reachable and the healthcheck works
  • Verify the service can generate a JWT
  • Verify we can authenticate using the JWT
  • Make note of any changes made to the service and the impact it has on generated MDA code for pipeline steps
  • All changes were made in foundation-security, extensions-security, aissemble-policy-decision, and aissemble-quarkus. This should not effect generated MDA code.

Test Steps

  • In a terminal, execute brew install --cask temurin@17 to install Java 17
  • Set Java 17 as your default version. Change your JAVA_HOME variable to point to the JDK 17 HOME location. Note: I left out instructions to do this because of the variety of shells being used.
  • Clone the aiSSEMBLE repository https://github.com/boozallen/aissemble.
  • Execute git checkout feature-java17 to checkout feature branch
  • In the project's root directory, execute the following and verify successful builds
    • mvn clean install -pl :aissemble-policy-decision-point -am Note: Make sure the image actually builds.
    • mvn clean install -pl :aissemble-policy-decision-point-chart -am
  • Execute
helm install --set image.tag=1.10.0-SNAPSHOT,image.imagePullPolicy=IfNotPresent,service.spec.type=LoadBalancer aissemble-policy extensions/extensions-helm/aissemble-policy-decision-point-chart/
  • Execute kubectl get pods, verify the aissemble-policy-decision-point-chart-* is running
  • Using Postman, run through the following
    • Send a Healthcheck request
    • Get a JWT token
      • Set method to POST
      • Set URL to http://localhost:8080/api/authenticate
      • Set the body type to JSON
      • Set body contents to: {"username": "aissemble","password": ""}
      • Click Send, verify you get a JWT token in the response
    • Validate JWT token
      • Set method to POST
      • Set URL to http://localhost:8080/api/pdp
      • Set the body type to JSON
      • Set body contents to {"jwt": "JWT_TOKEN","resource": "","action": "data-access"} where JWT_TOKEN is the token from the previous request
      • Click Send, verify you get the response PERMIT
@cwoods-cpointe cwoods-cpointe added the enhancement New feature or request label Sep 20, 2024
@jacksondelametter jacksondelametter self-assigned this Sep 20, 2024
@ewilkins-csi ewilkins-csi added this to the 1.10.0 milestone Sep 23, 2024
@carter-cundiff
Copy link
Contributor

OTS passed

@csun-cpointe
Copy link
Contributor

Test passed!
Send a Healthcheck request
Screenshot 2024-09-27 at 10 09 57 AM

Get a JWT token
Screenshot 2024-09-27 at 10 10 35 AM

Validate JWT token
Screenshot 2024-09-27 at 10 11 53 AM

ewilkins-csi pushed a commit that referenced this issue Oct 1, 2024
[#354] Modified PDP to build with Java 17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants