new lexik:jwt:generate-key command #655
Closed
Conversation
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
chalasr
force-pushed
the
master
branch
2 times, most recently
from
54da095 to
a10f88a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request will add a new command for creating new secret and public pem files based on lexik_jwt configuration using php openssl extension. The pem files will be generated in:
lexik_jwt_authentication.secret_keyparamaterlexik_jwt_authentication.public_keyparameterThe files will be generated using passphrase from
lexik_jwt_authentication.pass_phrasevalue.I also fix error/bug in LexikJWTAuthenticationExtension because container parameter
lexik_jwt_authentication.secret_keyandlexik_jwt_authentication.public_keynever set in this Extension (please see my 7fac306 commit)