authentication.jwt.expires fatal error

hijoncon

Hi @vasyl, I'm trying to extend the lifespan of my token. I got that example in your documentation. When I added it to my ConfigPress I could not able to authenticate. Is there anything I should do?

[aam]
;keep token valid for 30 days
authentication.jwt.expires = 2592000

{
    "reason": "DateTime::__construct(): Failed to parse time string (2592000) at position 4 (0): Unexpected character"
}

vasyl

hijoncon good catch. This is due to the fact that AAM expects this property to be a string that is evaluated by DateTime::__construct object.

Try to change your ConfigPress to something like this:

[aam]
; keep token valid for 30 days
authentication.jwt.expires = "+30 days"

In the next AAM release, I'll make sure that it properly handles the ttl as number of seconds.

Thank you.

hijoncon

Ok, that works for me, also you may want to update the docs. Thanks

vasyl

hijoncon already did. Thank you!

voivoed

Hi I'm hitting a problem trying to get authentication.jwt.expires to work and ended up finding this thread.

I've tried using both number of seconds and strings like "+30 days" as in your example above in the Configpress tab,, but when I request authentication tokens and go to the JWT tokens panel, all the tokens show an expiration date 17 hours (?) from now, it doesn't matter what I do. Is there anything else I should be doing?

Thanks!

vasyl

voivoed can you please post me exact ConfigPress that you are defining? I'll try to reproduce it on my dev instance.

voivoed

Ok, just after posting this I noticed the "[aam]" in your example and decided to try adding it to the top of the Configpress file, everything is working now. Maybe you could add that to the documentation? I searched but couldn't find mentions of that section being necessary in the Configpress file. Thanks! :-)

vasyl

voivoed the [aam] section is absolutely necessary because ConfigPress is based on the INI standard so all the settings have to be grouped. All AAM related settings should belong to [aam] section.

You can define your own section and technically get it programmatically. More details I'll disclose in the Dev Reference sometime soon.