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.

Sign up for GitHub

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

Jump to bottom

feat: add private-key-converter to README.md #94

Merged
merged 2 commits into from
Mar 2, 2024
Merged

feat: add private-key-converter to README.md #94

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4fbcdee
add private-key-converter to README.md
babblebey Feb 27, 2024
085911d
Update README.md
babblebey Mar 2, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -191,6 +191,12 @@ You can identify the format based on the the first line

### Converting `PKCS#1` to `PKCS#8`

- #### Using an Online Private Key Converter

Convert quickly using the Web interface at https://private-key-converter.vercel.app

- #### Using Node.js

If you use Node.js, you can convert the format before passing it to `universal-github-app-jwt`:

```js
Expand All @@ -210,7 +216,9 @@ const { token, appId, expiration } = await githubAppJwt({
});
```

But we recommend to convert the format using `openssl` before passing it to your app.
- #### Using OpenSSL

Convert the format using `openssl` before passing it to your app.

```
openssl pkcs8 -topk8 -inform PEM -outform PEM -nocrypt -in private-key.pem -out private-key-pkcs8.key
Expand Down