Tekton on OpenShift: authentication issue with internal OpenShift registry

From https://github.com/GoogleContainerTools/jib/issues/2074#issuecomment-579921534

I did a new test using the following parameters top of ocp3 and that fails using jib-maven 2.0.0

    - name: build-and-push
      image: gcr.io/cloud-builders/mvn
      command:
        - mvn
        - compile
        - com.google.cloud.tools:jib-maven-plugin:2.0.0:build
        - -Djib.from.image=registry.redhat.io/redhat-openjdk-18/openjdk18-openshift
        - -Djib.allowInsecureRegistries=true
        - -Djib.from.auth.username=my-user
        - -Djib.from.auth.password=my-pwd
        - -Dimage=$(outputs.resources.image.url)

If I add to the config too -DsendCredentialsOverHttp=true, then we got this error

[ERROR] Failed to execute goal com.google.cloud.tools:jib-maven-plugin:2.0.0:build (default-cli) on project rest-http: 
Build image failed: Failed to authenticate with registry docker-registry.default.svc:5000/test/sb-image 
because: server did not return 'WWW-Authenticate: Bearer' header: Basic 
realm=openshift,error="access denied" -> [Help 1]

[cmoulliard]

Here is the stack trace generated including the HTTP requests : https://gist.github.com/cmoulliard/2a0edd9f2e6e1f3b28539539021e2426

@chanseokoh

[chanseokoh]

@cmoulliard we’ve released Jib 2.1.0 with this fix. You should no longer see the error about server did not return 'WWW-Authenticate: Bearer' header.