Do you actually need to do the generation of keys in the build, or could you do that outside of the build and present the same ones each time? If you can do the latter, then you can just store them in env vars in the UI.
Thank you for your reply, I tried your suggestion but it didn’t like the public key!
The first time I tried it I got this error:
#!/bin/sh -eo pipefail# Unable to parse YAML # while scanning a simple key# in ‘string’, line 68, column 11: # '-----BEGIN PUBLIC KEY-----# ^ # could not find expected ':'# in ‘string’, line 80, column 45: # ... D8bdNZ+Vj+sN+L6L4QOy28CAwEAAQ=='# ^ ## ------- # Warning: This configuration was auto-generated to show you the message above.# Don’t rerun this job. Rerunning will have no effect. false
So I removed the last line of the public key: -----END PUBLIC KEY-----’ which makes the yaml valid, but now I get an error from LexikJWTAuthenticationBundle:
Unable to create a signed JWT from the given configuration.
I tried generating another key, but it ends with the same ==