feat(jans-agama): update htmlunit

[yurem]

closes #10447

• I confirm that there is no impact on the docs due to the code changes in this PR.

Closes #10465,

[dryrunsecurity]

DryRun Security Summary

The pull request involves removing the version specification for the htmlunit dependency in a Maven POM file, which is a standard practice, but maintaining overall dependency security requires regular review and updates of third-party libraries.

Expand for full summary

Summary:

The changes made in this pull request do not appear to introduce any significant security concerns. The code change is a removal of the version specification for the htmlunit dependency in the jans-auth-server/agama/engine/pom.xml file, which is a Maven project object model (POM) file. Removing the version specification is a common practice, as Maven can automatically resolve the latest compatible version of the dependency.

However, it's important to note that the security of the application depends on the overall dependencies and their versions used in the project. Regularly reviewing the dependency versions and updating them to the latest secure versions is a best practice for maintaining application security. Additionally, the project uses several third-party libraries, such as Rhino, Groovy, and Jans-related libraries, which should also be reviewed for any known security vulnerabilities. Keeping all dependencies up-to-date and monitoring for security advisories is crucial for maintaining the overall security of the application.

Files Changed:

• jans-auth-server/agama/engine/pom.xml: The changes in this file remove the version specification for the htmlunit dependency in the <dependencies> section of the POM file. This is a common practice, as Maven can automatically resolve the latest compatible version of the dependency.

Code Analysis

We ran 9 analyzers against 1 file and 1 analyzer had findings. 8 analyzers had no findings.

Analyzer	Findings
Sensitive Files Analyzer	1 finding

View PR in the DryRun Dashboard.

[mo-auto]

Error: Hi @yurem, You did not reference an open issue in your PR. I attempted to create an issue for you.
Please update that issues' title and body and make sure I correctly referenced it in the above PRs body.

[sonarqubecloud]

Quality Gate passed for 'Jans-Keycloak-Link'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed for 'SCIM API'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed for 'jans-config-api-parent'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud