autogen iat, the Issue At key

[rpcme]

right now we have nbf and exp. some providers require iat.

It would be nice to auto generate iat and compute exp based on the threshold, i.e. pass in '3600' and generate the values.

otherwise, all subclasses will need to compute it on their own, add Time::HiRes as a dep, etc.

if you would like me to try it on a branch to see how it would look, please let me know.

[jberger]

the difficulty, sad as it is, is testing. With only one hash key by default, I know the hash ordering. With two, (ie if iat and some test data) were include now I don't have known hash ordering. I suppose we could simply test with iat. Perhaps an attribute to which enables automatic inclusion of iat?

[rpcme]

Perhaps. My main concern is I don’t want to upend your stuff right now.

What we can do is : if I can get it “to work” in my new module, we can pull it up higher in the class hierarchy. If we find it’s too specific or can’t be generalized, it stays in the subclass.

On Apr 23, 2015, at 2:31 PM, Joel Berger [email protected] wrote:

the difficulty, sad as it is, is testing. With only one hash key by default, I know the hash ordering. With two, (ie if iat and some test data) were include now I don't have known hash ordering. I suppose we could simply test with iat. Perhaps an attribute to which enables automatic inclusion of iat?

—
Reply to this email directly or view it on GitHub #2 (comment).

[jberger]

how does https://github.com/jberger/Mojo-JWT/compare/set_iat look?