What would the full connection string look like?

postresql://postgres:password@host:port/db_name

Typical connection string?

yup. Looks good

We use full connection strings a lot, I think even managed db services at least on those I've tried just provides plain connection strings so yea

Unless you're doing something special with the individual fields xD

Nothing special.. will add full connection string! thanks. These are the two issues for this: - https://github.com/supertokens/supertokens-core/issues/220 - https://github.com/supertokens/supertokens-core/issues/221

Awesome! Looking forward to it!

hey all, I am working on a small product for which I am first building the backend. let's say I want to implement ST as my user auth solution and want to test it. would I need to set up the frontend as well so I can test various scenarios of the front auth-ing a user on the backend? or I could somehow test the backend part of the implementation alone? 🤔 all thoughts are appreciated! 🙏

Yeah you can, you can test it using postman, insomnia even curl if you like the terminal, you just have to create an endpoint on your backend so the program can make an http request into that endpoint or even if its a graphql api you can also test it using postman or insomnia

Postman is my weapon of choice. 🙂

but wait - there's something I don't understand. ST has a frontend SDK which should be responsible for sending initial auth data to the backend SDK, right? so, how could I test the backend part if I am missing the frontend? could please explain in the most simplistic terms so I could understand it? 🙏 🙂

So the backend (via our node SDK) exposes a few APIs that are consumed by the frontend. You can call those APIs manually using postman to test your backend.

The list of APIs exposed are: https://github.com/supertokens/frontend-driver-interface/blob/master/v1.7.0.md (Based on the recipes you have called

init

on)

@User which recipe are you using? - emailpassword - thirdpartyemailpassword - thirdparty - session Based on your answers, I can send you an example of what it's like to query an API manually to test if the core and the backend (APIs) are working or not.

Hey

@User do you know why i got failed connection using this?

Do im setting the variables wrong or something?

@User emailpassword for me, please. 🙂

Give me 5-10 mins please.. I'll get back with a reply

Sure, no worries, thanks for the help

@User can you run the docker command without the

-d

flag (in the last line) and show me what the error is?

Is weird because I try with the same credentials using heidisql and its works

The issue is that you are passing localhost in the docker image. That points to localhost inside the docker container and not your machine

Ohh

so you would need to pass the IP of your machine instead of localhost. And make sure that postgres is listening to that IP

Ok, going to check and let you know

@User , so for emailpassword API, I will show you how to call the signin API in your node process. I will assume the following: - You have integrated our SDK into your node process. - Your node process is running on

http://localhost:8080

(can use anything, but for this example, I will be using that). - Your

apiBasePath

is the default one (

/auth

) In Postman, do the following: - Put

http://localhost:8080/auth/signin

in the URL - Change method to

POST

- Click on Body > raw option - Choose JSON in the drop down that shows up next to the options - Paste the following in the body and click send:

{
  "formFields": [
    {
      "id": "email",
      "value": "test@example.com"
    },
    {
      "id": "password",
      "value": "testPassword"
    }
  ]
}

Cool, yeah it was that, also just another thing

This need to be added to pg_hba.conf