Cookie not created automatically

[RalpinMcDjango]

Hi guys,

As i understand since #753 the bundle should automatically return a secure and httpOnly cookie with the name provided in the config YAML.

This doesn't appear to be working on my environment right now. I'm testing this via Postman using Symfony 5 as the framework.

lexik_jwt_authenctication.yaml

token extraction settings

token_extractors:
    cookie:
        enabled: true
        name: Bearer
    authorization_header:
        enabled: false
        prefix:  Bearer
        name:    Authorization
    query_parameter:
        enabled: false
        name:    bearer

Any ideas why this might not be working as expected?

[chalasr]

Hey,

For backward compatibility reasons, we can't enable the feature based on the configured extractor (since one could have a similar cookie-adding logic which could break when upgrading).

For enabling this feature, you need to set another config option:

token_extractors: 
    cookie: 
        enabled: true
        name: BEARER
# ...
set_cookies:
    BEARER: ~

# Full config with defaults:
#  BEARER:
#      lifetime: null (defaults to token ttl)
#      samesite: lax
#      path: /
#      domain: null (null means automatically set by symfony)

[chalasr]

If you don't mind, I'll keep this issue open as a reminder, we need to document the new option (PR welcome :) )

[RalpinMcDjango]

Hey,

For backward compatibility reasons, we can't enable the feature based on the configured extractor (since one could have a similar cookie-adding logic which could break when upgrading).

For enabling this feature, you need to set another config option:

token_extractors: 
    cookie: 
        enabled: true
        name: BEARER
# ...
set_cookies:
    BEARER: ~

# Full config with defaults:
#  BEARER:
#      lifetime: null (defaults to token ttl)
#      samesite: lax
#      path: /
#      domain: null (null means automatically set by symfony)

That's perfect, thank you. I thought there might be some more configuration required.

If you don't mind, I'll keep this issue open as a reminder, we need to document the new option (PR welcome :) )

Not a problem at all :)

[RalpinMcDjango]

PR submitted

[chalasr]

Fixed by #763, Thank you very much @RalpinMcDjango