[Test] spec/lib/omni_auth/strategies/jwt_spec.rb | OmniAuth::Strategies::Jwt#decoded when timestamp claim is too skewed from present raises error
Test metadata
The following three specs were flaky. Combining into one because the solution is likely the same/similar for all.
Field |
Value |
File URL |
spec/lib/omni_auth/strategies/jwt_spec.rb#L126 |
Filename |
spec/lib/omni_auth/strategies/jwt_spec.rb |
Description |
OmniAuth::Strategies::Jwt#decoded when timestamp claim is too skewed from present raises error |
Test level |
unit |
Hash |
c9ed07a32fb331b7386a8614c2c1ffac9dc04102f |
Max expected duration |
< 27.12 seconds |
Test metadata
Field |
Value |
File URL |
spec/lib/omni_auth/strategies/jwt_spec.rb#L87 |
Filename |
spec/lib/omni_auth/strategies/jwt_spec.rb |
Description |
OmniAuth::Strategies::Jwt#decoded required claims is missing raises error |
Test level |
unit |
Hash |
571a003faa9e69607923f5f85a7c8553630be34c5 |
Max expected duration |
< 27.12 seconds |
Test metadata
Field |
Value |
File URL |
spec/lib/omni_auth/strategies/jwt_spec.rb#L69 |
Filename |
spec/lib/omni_auth/strategies/jwt_spec.rb |
Description |
OmniAuth::Strategies::Jwt#decoded when the HS384 algorithm is used decodes the user information |
Test level |
unit |
Hash |
f1709a9899be0baaf238ee345a07f4c002a335894 |
Max expected duration |
< 27.12 seconds |
Edited
by
Drew Blessing