golint has updated or dropped support for old Go versions several times,
causing breaks in our build. Vendor it locally to prevent this.

*: update go version

Add mention of `scopes` parameter in OIDC doc

Fix broken link to Bitbucket Cloud documentation

.travis.yml: fix golint import

Add Bitbucket connector

minor spelling correction

connector/saml: make unparsable (trailing, non-space/newline) data an error

Fixes #1304, if we want to be harsh.

However, I think if it was the user's intention to pass two certs, and
the second one couldn't be read, that shouldn't just disappear. After
all, when attempting to login later, that might fail because the
expected IdP cert data isn't there.
Signed-off-by: Stephan Renatus <srenatus@chef.io>

Support used self-signed certificates LDAP.

Format ldap.go

Format ldap.go: with a space for golint

with a space

Rename clientCA is to clientCert

Update ldap.go

modified the ldap client certificate file comments.

modified load ldap client cert error.

modified load ldap client cert error: fmt.Errorf("ldap: load client cert failed: %v", err)

Update go-jose to v2.1.8

Allow using GitHub Team slug instead of name via connector config option

release process: update quay notes

scripts,Makefile: nuke check-go-version

Fixes #1291
Signed-off-by: Stephan Renatus <srenatus@chef.io>

fix timeout bug for etcd3 client connect

Fix #1252

Signed-off-by: Stephan Renatus <srenatus@chef.io>

Signed-off-by: Stephan Renatus <srenatus@chef.io>

Finish GitHub org move

Signed-off-by: Stephan Renatus <srenatus@chef.io>

Signed-off-by: Stephan Renatus <srenatus@chef.io>

Signed-off-by: Stephan Renatus <srenatus@chef.io>

connectors/ldap: treat 'constraint violation' on bind as bad credentials

Some directory servers (I think it's Oracle) return

    Constraint Violation: Exceed password retry limit. Account locked.

when attempting to login too many times. While constraint violation can
mean many things, we're checking this as an error on BIND, so it's
more likely that something like this has happened than any other thing.

Hence, we should treat it as an "incorrect password" situation, not an
internal error.

It would of course be preferrable to surface more information about this
precise error (and similar ones), but I think this is beyond this small
change.
Signed-off-by: Stephan Renatus <srenatus@chef.io>