https-pem | signed PEM key and certificate ready | TLS library
kandi X-RAY | https-pem Summary
kandi X-RAY | https-pem Summary
Self-signed PEM key and certificate ready for use in your HTTPS server
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of https-pem
https-pem Key Features
https-pem Examples and Code Snippets
Community Discussions
Trending Discussions on https-pem
QUESTION
I am having an issue with validating the JWT on the server side end of my node/express app. The token is being generated in Identity Server in an asp.net core app. The token that is generated is an RS256 token type, which means a private key and public key need to be generated on creation in the Identity Server. What that means for me -
On the client side (Angular) I'm passing in the Bearer token on all requests once signed in. I need to authenticate that token somehow. The way to do that with a RS256 token type is to make sure the public key matches. I'm using
const jwt2 = require('jwt-simple');
For my JWT validation.
The issue is the secret, here is the jwt-simple documentation jwt-simple link. If I make the third value in decode false it works, because it's ignoring the secret/cert that is required.
I'm getting this error -
Error: error:0906D06C:PEM routines:PEM_read_bio:no start line
I'm making this validation in the middleware so all endpoints will hit it. I saw this issue - SO Similar Issue and ran those same commands. I'm still getting the error because the token doesn't really have anything to do with the certs because I'm getting it from the Identity Server project. So I need to retrieve the cert public key from that project.
How would I be able to send that cert in the token or retrieve that valid cert somehow? Hopefully, this made some sense. Any help would be appreciated.
v1 - (using the self signed server.crt as the cert and getting this error)
Error: Signature verification failed
App.js
...ANSWER
Answered 2018-May-30 at 14:43I dig a bit and here is my investigation:
From node-jsonwebtoken docs, your secret must be valid private key.
secretOrPrivateKey is a string, buffer, or object containing either the secret for HMAC algorithms or the PEM encoded private key for RSA and ECDSA. In case of a private key with passphrase an object { key, passphrase } can be used (based on crypto documentation), in this case be sure you pass the algorithm option
Also, It will be better to provide the 'RS256' as third param in encode
and decode
function.
Checkout below sample code:
app.js
QUESTION
I have tried everything on this thread with no luck. Node.js https pem error: routines:PEM_read_bio:no start line
I am trying to do a very simple request to the google API to ask for a channel's information.
Things I have:
- npm request installed
- A google API key - exported to an env variable
- I am using cloud9 (which is why the other solution may not have worked)
I can make a request to the yahoo weather API no problem using the same method.
...ANSWER
Answered 2018-Mar-25 at 19:46Give this a try instead. The query string parameters are not sent correctly, so the API responds that it could not find your key.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install https-pem
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page