Is it possible for admin and frontend have same users collections?

[Kotletka89]

I'm developing an app, where users can create account, and they should be able to access admin panel with some rights, and also use same account for frontend part

does this plugin works this way?

I wish to see the more docs about it

[Kotletka89]

I've encountered with some error, don't know how to fix it

[sourabpramanik]

I'm developing an app, where users can create account, and they should be able to access admin panel with some rights, and also use same account for frontend part

does this plugin works this way?

I wish to see the more docs about it

I can think of such use cases for obvious reasons,, maybe in future I can make it work using a single collection, but said that separation of concerns is also very important

[sourabpramanik]

I've encountered with some error, don't know how to fix it

How are you triggering this?

[engin-can]

I agree with @Kotletka89 . To me admin should be considered a role rather than a separate entity/collection.

[Rnbsov]

I agree with @Kotletka89 . To me admin should be considered a role rather than a separate entity/collection.

yeah, that's a fair point

I think this use case is more common

[Rnbsov]

Now I wonder, is it possible right now to implement such behavior with this plugin? Maybe by dublicating entries in both collections or something, but it sounds as bad idea.

because my current project requires such functionality, and I wish such a case would be considered

[Rnbsov]

@sourabpramanik would you like to implement such functionality, and how long would it take to implement such a use case in this plugin?

[Kotletka89]

I've encountered with some error, don't know how to fix it

How are you triggering this?

[sourabpramanik]

I've encountered with some error, don't know how to fix it

How are you triggering this?

The name that you use in the appClient function should be same as the name you have given in the appAuthPlugin which is "app" and your use "google" as the name in the appClient function

[sourabpramanik]

Also install the latest version, the usage of OAuth sign-in has changed

 const handleGoogleSignin = async () => {
    const res = await signin().oauth('google')
    if (res.isSuccess) {
      router.push('/admin')
    }
  }

[sourabpramanik]

@sourabpramanik would you like to implement such functionality, and how long would it take to implement such a use case in this plugin?

I am now planning to resolve the whole logic into the appAuthPlugin for all kinds of usage and deprecate admiAuthPlugin.

[Rnbsov]

@sourabpramanik would you like to implement such functionality, and how long would it take to implement such a use case in this plugin?

I am now planning to resolve the whole logic into the appAuthPlugin for all kinds of usage and deprecate admiAuthPlugin.

Omg! That's a great idea. You can't imagine how happy I'm hearing this! This would help me make my app so much faster! Appreciate your work and time, looking forward to this crucial update!

[Kotletka89]

@sourabpramanik how long it will take to implement this ?

[sourabpramanik]

@sourabpramanik how long it will take to implement this ?

Not too long but cannot commit any ETA for now

[sourabpramanik]

So this is what the minimal implementation will look like:

For app auth

authPlugin({
  name: "some-unique-name",
  providers: []
})

For admin auth

authPlugin({
  name: "some-unique-name",
  useAdmin: true,
  providers: []
})

What do you guys think?