When trying to connect amplication server to GitHub it gives me an error that the key must be an asymmetric key when using RS256. I don't know what is the issue. Is this a GitHub auth error or amplication error.
#GitHub secretorprivatekey error
orchid obsidian
gentle sandal
I had the same problem
The docs here (https://docs.amplication.com/running-amplication-platform/connect-server-to-github/) says that "\n" should be placed at the end of each line, then join them into one string. But that's not very accurate.
To solve it, I added the "\n" to the end of all the lines except the last one, then joined them together into a single string.
hot fog
@gentle sandal do you want to send a fix for the docs so others can find it later?
tardy sun
@gentle sandal thanks for noticing, we are now changing the page to clarify that the last line should not have a "\n". It will be live in a few minutes.
white knollBOT
GG @tardy sun, you just advanced to level 4!
orchid obsidian
I think including a simple example also might help
gentle sandal
<@963897301196238919> do you want to send a fix for the docs so others can find ...
Hi, I'm just seeing this.
Guess it's too late to make that contribution, huh?
hot fog
Thanks, it was fixed already
Feel free to pick any other issue you see with the label “open for community” and thanks for your support
fossil sand
Sorry to bring this up again. Still got the Problem. Do I understand correctly to double generate a private key? One in Step 5, one in Step 6. The one in step 5 I made a one-liner with \n, what about the one .pem coming from step6?
safe wraith
steps 1.5 and 1.6 are referring to the same cert. I'll udpate the docs