Closed SoylentGraham closed 7 months ago
ooof, I created a new private key, and down came a .pem
!
Copied the contents of that directly into the secret, and it's worked!
(someone else generated my initial private key + secret, and I guess copied the wrong thing - doing it myself was a bit more obvious what the content should be :)
Perhaps still, the docs could be clearer that the key is the contents of the .PEM
and not the key displayed in the app.
The error could also be better for users
It must be documented the SECRET_PEM
value MUST be the content of the .pem
file and not the base64
of the .pem
as it documented elsewhere in the GitHub docs.
as it documented elsewhere in the GitHub docs
if you could please point us to where it's documented, we will make sure it gets fixed
I have tried to use this action with a newly created internal github-app and get this error.
I guess it means my secret is wrong? Could I have formatted it incorrectly? Is it likely to be similar to this stackoverflow question? (PEM format, extra whitespace etc) https://stackoverflow.com/questions/75635389/secretorprivatekey-must-be-an-asymmetric-key-when-using-rs256
Client Secret
key that I generated (42 char hex string)SHA256:<base64 string XYZ0123/=>
SHA256:
prefix