Parsing the firebase private key on AWS Elastic beanstalk

Question

I am moving my firebase authenticated node.js application from Heroku to AWS Elastic Beanstalk. The private key is not parsing correctly. It is having trouble understanding the newline characters from the environment variables.

For reference I have already tried the solution found in this stackoverflow post: Node.js -Firebase Service Account Private Key won't parse

privateKey: process.env.FIREBASE_PRIVATE_KEY.replace(/\\n/g, '\n')

Unfortunately, as this works on Heroku, the same is not true for AWS Elastic Beanstalk. After logging the private key in the terminal I notice it is replacing the \n with simply 'n' and making no newline character at all.

Newline characters are not allowed while setting environment variables in the EB software configuration. Any new lines are replaced with just a single space.

Not sure if there is another way short of keeping the key directly in the code which I would like to avoid.

When adding properties in the software configuration, are you entering `\\n` instead of `\n`? Alternatively, replace the newlines with a symbol that doesn't appear in the key like `@`. — samthecodingman, May 20 '21 at 07:02
Does [this](https://stackoverflow.com/a/67563201/13130697) work? — Dharmaraj, May 20 '21 at 07:04
@samthecodingman - this worked, thank you. Just used `process.env.FB_private_key.replace(/\@/g, '\n'),` — J. Carpenter, May 20 '21 at 18:06

score 1 · Answer 1 · answered May 31 '22 at 14:52

The thing is Elastic Beanstalk removes an escape \ character from environment value.

So your private key, for example

-----BEGIN PRIVATE KEY-----\nXIaEvQIBKDAN...

becomes

-----BEGIN PRIVATE KEY-----nXIaEvQIBKDAN... and invalid

In case anyone needs some example, this is what I did.

As suggested in the comment above, I replaced all \n with @ and put the key on the EB env's Environment properties.

When my app runs, it will get the key like this

-----BEGIN PRIVATE KEY-----@XIaEvQIBKDAN...

So before using it, just replaced @ back to \n with

process.env.PRIVATE_KEY.replace(/\@/g, '\n')

Awelle · Answer 2 · 2022-04-29T16:57:57.207

I had this issue too. I needed to get it working ASAP. None of the solutions worked for me. A temporary hack I did was to push the key but hide some parts of it as env variables.

Something like:

admin.initializeApp({
  credential: admin.credential.cert({
    privateKey: `-----BEGIN PRIVATE KEY-----\nkjhgfdftyujklkjhgf${process.env.PRIVATE_KEY_CHUNK_1}VGHJKMJHGhgfhjkljhg----END PRIVATE KEY-----`,
     projectId:  process.env.PROJECT_ID,
    clientEmail:  process.env.CLIENT_EMAIL,
  }),
})

I figured if they don't have everything, it's sorta useless. Except there's some way to reverse engineer -ish a firebase private key.

score 0 · Answer 3 · answered Nov 22 '22 at 23:56

You can escape the \n with \\n. See the beanstalk documentation here:

https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/environments-cfg-softwaresettings.html

Values can contain any alphanumeric characters, white space, and the following symbols: _ . : / = + \ - @ ' "

Note Some characters in environment property values must be escaped. Use the backslash character () to represent some special characters and control characters. The following list includes examples for representing some characters that need to be escaped:

backslash () — to represent use \

single quote (') — to represent use '

double quote (") — to represent use "

So, for a private key, it could look like this:

-----BEGIN PRIVATE KEY-----\\nANdIERadKeBFsaNBgkqhkiG9w0EFA

And each place you need a newline, you just "double escape" the n.

I've tested it and it worked for me.

score 0 · Answer 4 · answered Dec 11 '22 at 09:26

I don't understand why this is even supposed to work. It is written in the AWS documentation that the length of the VALUE can be up to 256 characters and the private key of Firebase is over 1700 characters.

Environment properties and other software settings Docs

Parsing the firebase private key on AWS Elastic beanstalk

4 Answers4