jakartaee / jakartaee/authentication

Correct way to configure the TCK

Open
#220 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
27
Forks
35
PR merge metrics
No merged PRs in 30d

Description

I have manged, barring some challenges, to get the TCK passing with Tomcat 11. However, that required various configuration steps that seem rather hacky. I suspect I am not quite doing things the right way. I'd like to understand the right way to do these things so I can submit a PR to add the necessary configuration to the TCK to run with Tomcat.

I added to tomcat-11 profile to tck/pom.xml. This appears to the the correct way to do things so I am not concerned about these.

The configuration changes I am concerned about are:

  • arquillian.xml. Placed in tck/common/src/main/resources, sets the user name and password required to deploy the test WARs to Tomcat. Also sets a number of system properties required by the tests.
  • tomcat-users.xml. Placed in tck/common/src/main/resources, used to configure the user required to deploy the test WARs to Tomcat. Also creates a user required by some tests.
  • ProviderConfiguration.xml. It was necessary to modify this file as the application context identifier needed to be changed to match the naming used by Tomcat.

Pointers to better/correct ways for each of the above welcome.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the Tomcat 11 profile in tck/pom.xml and the configuration files under tck/common/src/main/resources: arquillian.xml, tomcat-users.xml, and ProviderConfiguration.xml. Compare the current settings with the configuration required to deploy and run the TCK on Tomcat 11. Done means the correct configuration is identified, the TCK passes without hacky external changes, and the necessary files can be added through a focused PR.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.