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
Appearance settings

[Security] make:security:custom #19809

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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 30, 2025
Merged

[Security] make:security:custom #19809

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
[security] make:security:custom 
Since MakerBundle `v1.59.0` - you can call `make:security:custom` to generate a simple, no-frills, custom authenticator based off the example in the docs.
  • Loading branch information
@jrushlow
jrushlow committed Apr 21, 2024
commit 6ae48a88672d49b781535a02f73ad971d4ca87b7
3 changes: 2 additions & 1 deletion 3 security/custom_authenticator.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,8 @@ Symfony comes with :ref:`many authenticators <security-authenticators>` and
third party bundles also implement more complex cases like JWT and oAuth
2.0. However, sometimes you need to implement a custom authentication
mechanism that doesn't exist yet or you need to customize one. In such
cases, you must create and use your own authenticator.
cases, you can use the ``make:security:custom`` command to create your own
authenticator.
Comment on lines +8 to +9
Copy link
Contributor Author

@jrushlow jrushlow Apr 21, 2024 •
edited
Loading

Choose a reason for hiding this comment

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

Hmm.. we reference the make:* command in the doctrine section like I have here.. But we use the code-block "syntax" else where in the doc's..

symfony-docs/security.rst

Line 727 in f7225d9

.. code-block:: terminal
I'm thinking we should make this a code block here?

Sidenote - I should probably change the

symfony-docs/doctrine.rst

Line 96 in f7225d9

You can use the ``make:entity`` command to create this class and any fields you
reference to a "code-block" style as well for consistency. Thoughts?

Copy link
Member

@javiereguiluz javiereguiluz Apr 26, 2024 •
edited
Loading

Choose a reason for hiding this comment

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

Yes, I think the terminal code block would be better because it stands out a lot and it's easier to scan for readers. Thanks!

Copy link
Member

Choose a reason for hiding this comment

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

I did this change while merging, so we now use a terminal code block.


Authenticators should implement the
:class:`Symfony\\Component\\Security\\Http\\Authenticator\\AuthenticatorInterface`.
Expand Down
Loading
Morty Proxy This is a proxified and sanitized view of the page, visit original site.