Skip to content

Why does this lib strictly checks on -----BEGIN RSA PRIVATE KEY----- in private key content? #65

@hirenchauhan2

Description

@hirenchauhan2

Hi,

I'm exploring this lib to subscribe platform events and process them using nodejs. I'm able to authenticate to SF using jsforce with JWT using my private key which does not have the RSA in the header, it's just -----BEGIN PRIVATE KEY-----. I don't know why does this library has to check about which type of key is used for authentication. Could you please help me understand this?

Thank you.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions