Skip to content
This repository has been archived by the owner on Dec 15, 2021. It is now read-only.

SEP31: SEP10 Has a valid token test too strict #151

Open
msfeldstein opened this issue Jul 8, 2020 · 0 comments
Open

SEP31: SEP10 Has a valid token test too strict #151

msfeldstein opened this issue Jul 8, 2020 · 0 comments

Comments

@msfeldstein
Copy link
Contributor

It looks like the test SEP10 > GET Challenge > POST Response > Has a valid token is failing if the jwt has extra fields in it. This is a totally valid thing to do so these tests shouldn't fail. Example is finclusive:

expect(received).toEqual(expected) // deep equality

Expected: ObjectContaining {"exp": Any<Number>, "iat": Any<Number>, "iss": Any<String>, "sub": "GCQJX6WGG7SSFU2RBO5QANTFXY7C5GTTFJDCBAAO42JCCFIMZ7PEBURP"}
Received: {"exp": 1594237594, "iat": 1594223194, "iis": "https://finclusive.com", "nbf": 1594223194, "sub": "GCQJX6WGG7SSFU2RBO5QANTFXY7C5GTTFJDCBAAO42JCCFIMZ7PEBURP"}
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant