Bump docker/build-push-action from 2 to 4 #40
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
With protocol plugins such as mqtt, or stomp, when they accept an incoming connection, immediately after, an internal amqp connection is created and the credentials received during the initial connection are passed to the internal amqp connection. With AMQP 1.0 plugin things are different. It only creates an internal amqp connection when a session is created. However, the full credentials, i.e. username and password are received during the initial connection establishment phase. During that phase the user is authenticated and its username is kept in User record. However, when a session is established and the plugin has to create an internal amqp connection, given that we are using Oauth2 backend, we still need to pass around the token as password. However, at this point we no longer have it. Therefore, to have to preserve the password. This PR suggests to optionally keep the token in the password attribute of the #user record and #auth-user record for auth backend which are token based such as oauth2. Other backend such as internal, http or ldap, do not need to preseve the initial password because to authenticate the internal amqp connection, they support "password-less" authentication, i.e. they only check the user exists.
Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 2 to 4. - [Release notes](https://github.com/docker/build-push-action/releases) - [Commits](docker/build-push-action@v2...v4) --- updated-dependencies: - dependency-name: docker/build-push-action dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
the
dependencies
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps docker/build-push-action from 2 to 4.
Release notes
Sourced from docker/build-push-action's releases.
... (truncated)
Commits
3b5e802Merge pull request #784 from crazy-max/enable-provenance02d3266update generated contentf403dafrevert disable provenance by default if not set1104d47Merge pull request #781 from crazy-max/disable-provenance838bf90update generated content337a09ddisable provenance by default if not set37abcedMerge pull request #760 from crazy-max/test-envs67109bctest: move envs to jest configd1b0eb0Merge pull request #759 from crazy-max/fix-provenance-inputa0635feupdate generated contentDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)