Use basic auth instead of JWT in tests.

[imeredith]

Description

@vivek seeing occasionally flaky tests that I believe are due to JWT not setting the user properly. Will be documenting it in a ticket for you to take a look at

See JENKINS-XXXXX.

Submitter checklist

• Link to JIRA ticket in description, if appropriate.
• Change is code complete and matches issue description
• Appropriate unit or acceptance tests or explanation to why this change has no tests
• Reviewer's manual test instructions provided in PR description. See Reviewer's first task below.
• Ran Acceptance Test Harness against PR changes.

Reviewer checklist

• Run the changes and verified the change matches the issue description
• Reviewed the code
• Verified that the appropriate tests have been written or valid explanation given

[cliffmeyers]

Should @Ignore be used so we can see in reports that they are actually skipped?

[vivek]

@imeredith Can we try something simple first, that is move System.setProperty("BLUEOCEAN_FEATURE_JWT_AUTHENTICATION", "true"); in static initializer. Something like:

static {
        System.setProperty("BLUEOCEAN_FEATURE_JWT_AUTHENTICATION", "true");
}

This will clear up any race condition that might be causing it not set at runtime?

[imeredith]

I am trying that but i dont see how that can fix anything given we set that prop in BaseTest

  public BaseTest() {
        System.setProperty("BLUEOCEAN_FEATURE_JWT_AUTHENTICATION", "true");
        j = new JenkinsRule();
    }

[vivek]

@imeredith thats inside constructor, static blocks are loaded during class load time and much before JenkinsRule or anything else gets setup. I think it's worth a shot.

[imeredith]

@vivek That static block thing didnt work. Merging this for now because it is blocking other people from getting things done. Can we add them back in if we figure it out.

[vivek]

@imeredith 👍

[i386]

Cherry picked to release branch