Hmmmm

Can you see the logs in the core?

And the query it using the node process and see if you can see API call logs being appended?

If you are using docker for the core, you can use docker logs

Else in the installation place, there is a logs folder

@User I've cleared out the info and error log files. It seems to be working now. Thanks a lot 🙂

oh! what was the issue?

Hi, SuperTokens could be used to authenticate several microservices, right?

we dont have machine to machine auth yet..

what exactly is your use case?

Can I use it as a verification centre for my microservices?

2/5 microservices that can be entered by the user

so it can be used to authenticate frontend clients to your backend API layer

but to authenticate backend services with each other, we don't have that yet

Any projection?

in terms of timeline for that feature?

Yeap

not anytime in the next 6 months unfortunately.

But you can use other services for this, or just use something as simple as an API key

and use those along with SuperTokens for frontend / backend session management..

Could you expand the API key a bit more?

Simply put, you could associate each microservice with some API key (some random string in the env var). And accept requests only if the request's

Authorization

header contains the API key

an even simpler method would be to put all your microservices in a VPC so that they are only reachable to one another.. this way they can just trust each other, and don;t need an API key at all

Thank you, now I understand the idea better I'll check the repos to see if it can help in any way.

Cool’

Hi, is there any working example/demo of supertokens session management for angular-node?

@raviagheda , there isn’t a demo for that.. but have a look at the session recipe docs. It has a quick setup section.

Yeah!

One more thing It is required to use axios or fetch only to make api call?

Yes. What else would you want to use?