[SOLVED] Multiple user accounts for 1 user

[versed girder]

I was wondering if someone has a smart solution for my problem 🙂
I am working on a project where a customer works at different companies. The customer creates an account at my app for Company1, completes his profile settings and wants to add his second account for Company2 to the same profile account as Company1. Both with OAUTH.
I can create a table in between as relation table from User Account to Profile, but i still have an issue. Everything the customer does when he is logged in as Company1 its documents will be created with his current userId. When he logs in as Company2 then he no longer has permission to edit them.

Does someone has a smart solution that i didnt think of?

[scarlet otter]

Appwrite had something called identities where an identity is an oauth2 provider account. A user can have multiple identities. To create another identity, have an active session and do the oauth2 flow again.

[versed girder]

But when it is a different emailaddress?

[scarlet otter]

Yup, that's why we created identifies

In 1.5.5, you can go to Auth > User and there's an identities tab

[versed girder]

omg, that is so awesome!

[versed girder]

Getting a bad request when i OAuth in the current session, and starting a new login request. I am using createOAuth2Token, is that the correct one to add an extra identity?

Ah, i think i need createOAuth2Session

Which isnt available in node-appwrite (yet?)

[scarlet otter]

Weird I don't see how that error would be returned for the create oauth2 token API call 🧐

[versed girder]

I am looking at the problem. I am using the cookie i got from the first authentication, that should be fine i guess?

And then this happens

[versed girder]

I forgot to reply, sorry 🙂

Ah fixed now. The oauth endpoint was trying to set the cookie again.

[versed girder]

But now there is a new user created, not a new Identity

[scarlet otter]

Does the browser have the users session?

[versed girder]

it has the session as a cookie, if that is what you are asking

I think i really need the CreateOAuth2Session

[scarlet otter]

The Appwrite session needs to be in the browser so that the API call with Appwrite is authenticated

[versed girder]

Ah, so client side it is

[versed girder]

I have been looking into a way to get the client session up and running, where i have a SSR session in use. I have my cookie in the browser, but cant figure out a way to setup the client with this info. Does anyone have a working example or tips?

[scarlet otter]

What's your Appwrite endpoint? You probably need to try and set a cookie that would make it compatible with appwrite too

[versed girder]

cloud.

Working with localhost in dev mode

[scarlet otter]

Could still be 3rd party cookies 🤷‍♂️

I would inspect the network traffic to see whats being passed to Appwrite for the redirect request

[versed girder]

Yeah, i am running now into a new problem. All of a sudden i get 'TypeError: e._formData.get is not a function'. Research online does give some results about appwrite usage

I am closing my eyes for now, driving me crazy these problems 🥲

[scarlet otter]

I've seen this when the web sdk is used in a SSR runtime

[versed girder]

It doesnt seem to be the case

hmm, possible the other way around, the node-appwrite in client side

[scarlet otter]

The new RC node sdk shouldn't have this problem

[versed girder]

I have changed my code to fully client side, with JWT for server side. Thanks for the help

{SOLVED} Multiple user accounts for 1 user