Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[Security] defer log message in guard authenticator#29323

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
fabpot merged 1 commit intosymfony:3.4fromeschultz-magix:defer_guard_log_message
Dec 10, 2018

Conversation

@eschultz-magix
Copy link
Contributor

@eschultz-magixeschultz-magix commentedNov 26, 2018
edited by nicolas-grekas
Loading

prevent an unnecessary log message if the guard authenticator does not support the current request

QA
Branch?3.4
Bug fix?yes
New feature?no
BC breaks?no
Deprecations?no
Tests pass?yes
Fixed tickets-
LicenseMIT
Doc PR-

This PR defers log messages about "getCredentials()" method calls if more than one guard authentication provider is used. The method is only called if the provider supports the request. The log message may be confusing during development.

@eschultz-magixeschultz-magix changed the titledefer log message in guard authenticator[Security] defer log message in guard authenticatorNov 26, 2018
}

// abort the execution of the authenticator if it doesn't support the request
if (!$guardAuthenticator->supports($request)) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

would it be useful to add a new log in this block then?

Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Maybe it helps debugging. I have added two more log messages.

prevent an unneccessary log message if the guard authenticator does not support the current request
@chalasrchalasr added this to the3.4 milestoneDec 9, 2018
@chalasrchalasr changed the base branch frommaster to3.4December 9, 2018 16:00
@chalasrchalasrforce-pushed thedefer_guard_log_message branch fromf67a317 to21c3030CompareDecember 9, 2018 16:01
@fabpot
Copy link
Member

Thank you@eschultz-magix.

@fabpotfabpot merged commit21c3030 intosymfony:3.4Dec 10, 2018
fabpot added a commit that referenced this pull requestDec 10, 2018
…ltz-magix)This PR was merged into the 3.4 branch.Discussion----------[Security] defer log message in guard authenticatorprevent an unnecessary log message if the guard authenticator does not support the current request| Q             | A| ------------- | ---| Branch?       | 3.4| Bug fix?      | yes| New feature?  | no| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets | -| License       | MIT| Doc PR        | -This PR defers log messages about "getCredentials()" method calls if more than one guard authentication provider is used. The method is only called if the provider supports the request. The log message may be confusing during development.Commits-------21c3030 [Security] defer log message in guard authenticator
This was referencedJan 6, 2019
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@fabpotfabpotfabpot approved these changes

@nicolas-grekasnicolas-grekasnicolas-grekas approved these changes

@chalasrchalasrchalasr approved these changes

+1 more reviewer

@ro0NLro0NLro0NL approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Projects

None yet

Milestone

3.4

Development

Successfully merging this pull request may close these issues.

6 participants

@eschultz-magix@fabpot@nicolas-grekas@ro0NL@chalasr@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp