Rui Yang

Hi @drahnr , I have noticed the commit history is a bit messing up. To fix it, the easiest way IMO is - git checkout a new branch from latest...

The error in unit test: ``` # github.com/concourse/concourse/worker/runtime worker/runtime/backend_test.go:551:32: unexpected comma; expecting ] FAIL github.com/concourse/concourse/worker/runtime [setup failed] FAIL ``` you can join contributors team in concourse/governance to view the build...

Hi, have you found anything helpful in the doc https://concourse-ci.org/vault-credential-manager.html#vault-approle-auth ?

If you have access to concourse web node log, you should see some logs related to vault creds manager, especially when web node restarts.

Hi, in your OIDC flags are you setting a key to `username`? Also in the Onelogin returing claims, is there a `name` or `username` field? The error is likely coming...

For the configure with `--oidc-scopes`, if you are trying to use groups matching, there is a bug https://github.com/concourse/concourse/issues/6435

@tkallenberg-tw is your issue resolved now? FYI we are going to release a patch version to fix OIDC connector. So if there is anything you want to add to the...

Without configuring --oidc-user-name-key, the default key is `name`, which should be available in the claims returned by onelogin based on the doc you posted. Is it possible that the user...

@rikkuness no concourse doesn't provide a way to config the `insecureSkipEmailVerified`. However in your case you can config `--oidc-scope` to exclude `email` scope to bypass the check (noted it might...

I think the problem is how concourse finds out put-only resources (as in job outputs) that need check here https://github.com/concourse/concourse/blob/master/atc/db/check_factory.go#L157-L162