Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Magic JWT verification #3

Open
giannifiore opened this issue Jan 12, 2022 · 0 comments
Open

Magic JWT verification #3

giannifiore opened this issue Jan 12, 2022 · 0 comments

Comments

@giannifiore
Copy link
Contributor

User Stories

As a Rebrandly developer,
I want Rebrandly customer to copy and paste a token into their middleware configurations,
So that I can pack multiple options and technical settings in a way that is transparent to customers

Acceptance Tests

[should verify that the token incorporates the alias hostname]
Given a valid Rebrandly token for aliasing (a JWT),
Given the middleware is set up with the token passed as option,
When the server is launched,
Then the token is decoded and the alias hostname is derived out of the JWT

[should verify that the token is signed by Rebrandly]
Given a valid Rebrandly token for aliasing (a JWT),
Given the middleware is set up with the token passed as option,
When the server is launched,
Then the JWT signature is verified against the Rebrandly public key

[should disable itself in case the token was not signed by Rebrandly]
Given an invalid Rebrandly token for aliasing (a JWT),
Given the middleware is set up with the token passed as option,
When the server is launched
Then the MW prints a warning and disables itself (no-op) in a way that the global flow continues as usual

@giannifiore giannifiore added this to the Stable version milestone Jan 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant