Simple Heroku Login

[jandolina]

There are several examples of authenticating a user in Heroku in this collection, they are considerably more complex than using the web based login (heroku login). When I was using bash, prior to writing a plugin I could call "heroku login" now that I am in the SFDX Plugin framework, that is not an option. Unfortunately shelljs.exec('heroku login') just hangs when you try to open the browser, it also hangs when you supply the -i option and try to do things through the command line.

One issue with the examples, is that they are using an existing project url, I am trying to push to a project.

Is it possible to use the web login from within an sfdx plugin?
If not...
Which heroku authentication method in this library would be the best to focus on?

[mshanemc]

I have a couple instances that go through heroku’s web login because the api token isn’t allowed (both relate to heroku connect). In those instances, I’m using puppeteer. The goal of those commands is CI kinda stuff (no user there to type in anything). What are you trying to make?

…

On Oct 14, 2020, at 10:31 PM, Joe Andolina ***@***.***> wrote:  There are several examples of authenticating a user in Heroku in this collection, they are considerably more complex than using the web based login (heroku login). When I was using bash, prior to writing a plugin I could call "heroku login" now that I am in the SFDX Plugin framework, that is not an option. Unfortunately shelljs.exec('heroku login') just hangs when you try to open the browser, it also hangs when you supply the -i option and try to do things through the command line. Is it possible to use the web login from within an sfdx plugin? If not... Which heroku authentication method in this library would be the best to focus on? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[jandolina]

Shane,
Thank you for the reply. I have a bash script that builds a IoT Scaffold and am translating it to an SFDX plugin for ease of use and to reach a bigger audience. The scaffold makes a Connected app, a Flow, and all the supporting objects needed to run the flow. From there it spins up a Heroku server that exposes an endpoint. Heroku takes care of the Salesforce authentication so that calls to the endpoint can be made by devices who may not be able to negotiate an oauth connection.

I was able to get everything working with the Bearer token and the HEROKU_API_KEY. The only problem there is that the user had to set the credentials outside the script.

As you can expect, once that was working I found my preferred solution.
child_process.execFileSync('heroku', ['login'], {stdio: 'inherit'}); // Totally launches the browser

Thanks for the support.

[mshanemc]

If you're deploying the app, use the heroku:repo:deploy. There's some ways to pass in environment variables that can be the credentials For example, https://github.com/mshanemc/align/blob/66b71f859e0dc208c68eb427723792189256ac6c/orgInit.sh#L8

…

On Thu, Oct 15, 2020 at 10:09 AM Joe Andolina ***@***.***> wrote: Shane, Thank you for the reply. I have a bash script that builds a IoT Scaffold and am translating it to an SFDX plugin for ease of use and to reach a bigger audience. The scaffold makes a Connected app, a Flow, and all the supporting objects needed to run the flow. From there it spins up a Heroku server that exposes an endpoint. Heroku takes care of the Salesforce authentication so that calls to the endpoint can be made by devices who may not be able to negotiate an oauth connection. I am all done with moving from bash to sfdx with exception of my heroku function. Do your puppeteer examples work for logging in to spin up a new app? From what I can tell you need a response from getMatchingApp. Since I don't have an app yet, I think I am in a pickle. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#86 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABAQPHAZW5ZRRHAEZOXVZ3DSK4GBVANCNFSM4SRNHZBA> .