Hi,
I'm currently setting up a HTTPS connection for my companie's Jenkins server.
We have several pipeline builds, that require passwords to be executed, which are set up as build parameters.
Our developers mainly use Blue Ocean as GUI, so they set all build parameters over Blue Ocean.

The issue:
If a HTTP connection is used, the password parameter has a defaultValue set.
If a HTTPS connection is used, the password parameter has no defaultValue set and therefore, the build can't be started. Only, if a value is given (no matter if it is correct or not), the build starts.
Since we want to ease up the build process and accessability of Jenkins for our developers, it is quite annoying to always manually type in a password.

Since the value is set in HTTP and only doesn't work, when a HTTPS connection is used, I assumed this probably isn't the intended behaviour and hence, I opened up this ticket.

I tried a HTTPS connection with HAProxy and with native HTTPS (over port 8080) enabled, both with the same behaviour.

How to reproduce:
Create this declarative pipeline example and run it over the Blue Ocean GUI, when using a HTTP connection and when using a HTTPS connection.

pipeline {
    agent none
    options {
        disableConcurrentBuilds()
        buildDiscarder(logRotator(numToKeepStr: '1'))
    }
    parameters {
        password(name: 'Upload_Password', description: '', defaultValue: '123')
    }
    stages {
        stage('Test something') {
            agent {
                node {
                    label 'master'
                }
            }
            steps {
                echo "HELLO"
            }
        }
    }
} 

The expected behaviour

The password parameter input field in the Blue Ocean GUI should always be set to the defaultValue, no matter if HTTPS or HTTP is used.