Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Use underlying library to decide which verifier to use based on header
#454 On the authenticator side I think the better approach is to use the underlying api to decide which verifier to use based on the header. On the generator side you are in control so I don't think you need an abstraction. Now except for the original MacVerifier I'm not sure how to create a Key but I think that's up to whoever injects the key into the authenticator.. I preserved existing functionality allowing secret key to be converted to SecretKey. Allow secret to be a PEM with associated algorithm
- Loading branch information
Garry
committed
May 18, 2016
1 parent
8900736
commit c7c8813
Showing
1 changed file
with
69 additions
and
9 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters