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

Allow leeway when validating iat and nbf claims #12

Closed

Conversation

anderslauri
Copy link

This PR enables support for leeway through a defined interface, the underlying claims implementation can opt to implement this interface, as is the case of StandardClaims. Fairly basic and small change of scope. I did not apply changes for MapClaims although I did to provide an attempt however the scope change would be to major.

Please provide feedback. Thank you.

@anderslauri
Copy link
Author

anderslauri commented May 15, 2021

Let me resolve these conflicts. I see the previous compilation issue was due to non existing Go 1.12 support for Time.Duration unit. Go 1.12 support required for this project?

@ah-f3
Copy link

ah-f3 commented May 20, 2021

Hi @anderslauri - Thanks for the PR.

We initially forked this repository to fix the security vulnrability mentioned here: dgrijalva#422 as the library author was unresponsive.

After some time the owner has responded and is discussing transferring ownership of the repository to a group of people who have track record maintaining OSS projects.

Here's discussion over the changes dgrijalva#462.

It's likely that Form3 will migrate over to using the upstream project again and recommend people also move to a community maintained project.

I will do a review of this PR and look to create a release for you to use with this functionality, but be warned that the group of new maintainers may not want this functionality and may not include it in future versions.

@niclasgeiger
Copy link

Thanks for the reply! I fear that this will still not be usuable because of dgrijalva#458
So if we use the ParseWithClaims function, you can only use MapClaims if I am not mistaken...

@niclasgeiger
Copy link

Thanks for the reply! I fear that this will still not be usuable because of dgrijalva#458
So if we use the ParseWithClaims function, you can only use MapClaims if I am not mistaken...

nevermind - this should work. Had a pointer error

@Waterdrips
Copy link

Ill cut a release when I'm back at my work computer. Thanks for the contribution

@niclasgeiger
Copy link

Any updates here? We are currently using the forked version of Anders and would love to switch back to this library if possible

@james-d-elliott
Copy link

It would probably be advisable to remake this PR in the new maintenance repository. Please see dgrijalva#462

@anderslauri
Copy link
Author

It would probably be advisable to remake this PR in the new maintenance repository. Please see dgrijalva#462

Right. Thank you. Looks like this fork did evolve into a project. I will have look and provide a PR.

@joshua-hill-form3
Copy link

This fork is now archived.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants