testing within Docker

richb201

I am developing inside a Docker container on my laptop. As part of my applications workflow my user sends a passwordless login email to a fake "employee email". The fake employee (for this test) opens the email and presses the link inside it and get's into my application (running under CI in Docker) on my localhost. I am able to send out the email from Docker with no issue. But how can someone clicking on the link in the email connect to http//:localhost/Configure/test.php running in my container for this test when they are on a different machine? I tried replacing the OAuth IdP login URL: with http://:my public ip address:8080/Configure/test.php but I get "localhost refused the connection". I think this is because the link in the email is

http://localhost:9011/oauth2/passwordless/36gB9ek8YGDZ0TLly8_WybwHaE_jcyYqcDHaMolUc8E?tenantId=34303566-6466-3234-6565-656233663263&client_id=32688330-1630-4e0d-a4de-8ae45c3ca527&metaData.device.name=Linux%20Chrome&metaData.device.type=BROWSER&redirect_uri=http%3A%2F%2F69.124.176.183%2Findex.php%2FConfigure%2FMyFormEmployees&response_type=code&timezone=America%2FNew_York

Why is the "localhost" not being replaced with "69.124.xx.xx" ? I have set in "login URL" to http://69.124.xx.xx:9011/Configure/MyFormEmployees but the link in Applications/view/OAuth IdP login URL keeps referring back to localhost.

I had a consultant add in ngrok so I could reach from another PC into my fusionauth:9011. But again, the link in the email still says localhost like above. What to do?

richb201

I am very close to solving this. If I can get the link in the email to start with http://http://0dae7c5e60b3.ngrok.io/ all would work. Should I be working with the email template or is that for something else?

One more thing. I am getting an error message from fa that I am missing the client_id. Is a client_id and a user_id (returned from registration) the same thing?

dan

Should I be working with the email template or is that for something else?

I'd look at email templates and tweaking those, yes. https://fusionauth.io/docs/v1/tech/email-templates/email-templates/ has some docs about this.

Is a client_id and a user_id (returned from registration) the same thing?

Nope. client_id represents an application in FusionAuth. user_id represents a user.

Hope that helps, glad you're getting close!