Support for JSON needed for the 2fa_login endpoint about 2fa HOT 5 CLOSED

I see that's definitely a limitation. Interesting that you're the first one bringing that up, you're definitely not the first one using the bundle in a (JSON) API.

I believe it can be solved relatively easily, by providing a config option to configure JSON request format and changing a few things in the code. I'll probably go with something like this:

# config/packages/security.yaml
security:
    firewalls:
        your_firewall_name:
            # ...
            two_factor:
                request_format: json  # This to switch to a JSON payload

from 2fa.

Defining the format in the configuration file would be okay.
May I take the liberty to suggest the name for this configuration option? I think that payload_format would be a nice self-explaining configuration option name. However, it may be even better to support json without the need to set the configuration option. But I guess setting the format in the configuration file is good enough.

from 2fa.

However, it may be even better to support json without the need to set the configuration option. But I guess setting the format in the configuration file is good enough.

True, it should actually be possible to determine the payload format and switch to JSON. I have to try that out :)

from 2fa.

v5.4.0 relased, which supports JSON payloads.

Info: https://github.com/scheb/2fa/blob/5.x/doc/api.md#json-data

from 2fa.

I executed composer update scheb/2fa and composer brought scheb/2fa to v5.4.2.
My check_path endpoint now works with these payload formats: application/json and application/x-www-form-urlencoded without changing anything in configuration files.

Thank you for the trouble.

from 2fa.