Are these instructions upto date and works for the currently available repo in github?\

While doing step 4 (from your list), you should have

./startTestingEnv --wait

running on a shell.

yes, it ran. then I broke it. Should I keep it running for further steps?

Yes. Keep it running all the time

Do not stop that process.

ok, will try

And while that's running, do step number 5 onwards in https://github.com/supertokens/supertokens-core/wiki/Building-from-source

Then you will not run into any problem.

ok, will do.

Hurray! it got installed and "supertokens start" started the process.

Awesome.

Hi everyone, I recently came across supertokens and wanted to get started. I am using nodejs+mongodb and react on frontend. I want to create SAAS application just wanted to know if I want to implement a adin user and each admin user will have some more users under him with specific permissions or roles then is it possible to implement such thing?

Hi @User , we currently do auth + sessions only. The features we provide for access control are limited to: - Putting the user's role in their session - Fetching a user's role on the backend, from their session - Fetching a user's role on the frontend, from their session. - Changing a user's role in a session in an API. You can checkout something like https://www.osohq.com/ for more features of access control. Use them for authorisation, and use SuperTokens for authentication.

Hello everyone. I am trying to get supertokens to run with nestjs and followed the guide on the website. Some functions are marked as deprecated though. https://supertokens.io/docs/session/nestjs/guide#6-add-the-supertokens-error-handler

@User you can import the

errorHandler

from

supertokens-node/framework/express

instead

I believe that that would be the only one that's showing the deprecated warning? Or is there some other as well?

Thanks for your reply 👍 No, I think that's it. But the supertokens.service.spec.ts fails the test, because of ConfigInjectionToken. I am new to Nest too, I am not sure how to test @inject properly.

@User can you please help with this?

Hi, why do you want to test

@inject

? if it's just the test generated by default you can safely ignore(/delete) it if you don't want to add any meaningful test there

I assumed you are supposed to do that. Got a bit confused since generated boilerplate usually shows best practice, no?

It's not that important though, I was just curious

Well, yeah, testing your services is a best practice 😄 so if you want to make that test run, you'd need to add the provider for

ConfigProviderToken

into the testmodule as well

you can see how to add the provider in

auth.module.ts

, you basically need to do the same thing in the spec file (with test values of course).

So you'd end up with something like this:

ts
import { Test, TestingModule } from '@nestjs/testing';
import { ConfigProviderToken } from "../config.interface";
import { SupertokensService } from './supertokens.service';

describe('SupertokensService', () => {
  let service: SupertokensService;

  beforeEach(async () => {
    const module: TestingModule = await Test.createTestingModule({
      providers: [
        {
          useValue: {
            appInfo: {
              apiDomain: 'http://localhost:3000',
              websiteDomain: 'http://localhost:3001',
              appName: "LTLocalTest"
            },
            connectionURI: "https://try.supertokens.io" ,
            apiKey: undefined,
          },
          provide: ConfigProviderToken,
        },
        SupertokensService],
    }).compile();

    service = module.get<SupertokensService>(SupertokensService);
  });

  it('should be defined', () => {
    expect(service).toBeDefined();
  });
});

That makes sense 😄 Thanks!

thank you @User

Are there any other alternatives for authorization? I will surely check https://www.osohq.com/ thanks for the link.

@User I don’t know of any other that only do authorisation. There r open source libs for each language. Do you use nodejs?

yes nodejs I have MERN stack project

I see. Will get back about some frameworks soon.