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

Commit9422f7f

Browse files
committed
minor#10642 Corrected typo (obax)
This PR was submitted for the master branch but it was merged into the 4.1 branch instead (closes#10642).Discussion----------Corrected typo<!--If your pull request fixes a BUG, use the oldest maintained branch that containsthe bug (seehttps://symfony.com/roadmap for the list of maintained branches).If your pull request documents a NEW FEATURE, use the same Symfony branch wherethe feature was introduced (and `master` for features of unreleased versions).-->Commits-------9f17c96 Update custom_authentication_provider.rst
2 parentsc3c7bfd +9f17c96 commit9422f7f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

‎security/custom_authentication_provider.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ How to Create a custom Authentication Provider
1414

1515
Symfony provides support for the most
1616
:doc:`common authentication mechanisms</security/auth_providers>`. However, your
17-
app may need to integrated with some proprietary single-sing-on system or some
17+
app may need to integrated with some proprietary single-sign-on system or some
1818
legacy authentication mechanism. In those cases you could create a custom
1919
authentication provider. This article discusses the core classes involved
2020
in the authentication process, and how to implement a custom authentication

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp