# Multiple clients each using LoginAsGuest locally share the same account

**URL:** <https://community.coherence.io/t/multiple-clients-each-using-loginasguest-locally-share-the-same-account/480>\
**Category:** Help\
**Created:** [March 23, 2024, 9:50pm UTC](https://community.coherence.io/t/multiple-clients-each-using-loginasguest-locally-share-the-same-account/480 "2024-03-23T21:50:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kevin](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/kevin/32/410_2.png) [@Kevin](https://community.coherence.io/u/Kevin)\
**Post date:** [March 23, 2024, 9:50pm UTC](https://community.coherence.io/t/multiple-clients-each-using-loginasguest-locally-share-the-same-account/480/1 "2024-03-23T21:50:24Z")

</div>

I’m noticing that when I run multiple clients, each of which performs a `LoginAsGuest` call this results in a message in the console from the Coherence SDK saying:

```auto
AuthClient: You have to call Logout before attempting to log in again. You're currently logged in as {UUID}

```

What implications does this have? I would have assumed that each client would be able to login as a seperate guest account. Note: I have seen in the documentation how this guest account is stored locally, but how does this influence communicating with the Coherence cloud services?

---

<div class="post-metadata">

**Author:** ![miguel-coherence](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/miguel-coherence/32/101_2.png) [@miguel-coherence](https://community.coherence.io/u/miguel-coherence)\
**Post date:** [March 25, 2024, 10:30am UTC](https://community.coherence.io/t/multiple-clients-each-using-loginasguest-locally-share-the-same-account/480/2 "2024-03-25T10:30:02Z")

</div>

Hiya Kevin!

Unfortunately this scenario is not supported out of the box, the credentials are stored in disk, and when you launch several instances of the same installation, Unity will check the stored credentials from the same file path. We have no way of uniquely identifying an instance.

Currently we attempt to refresh the stored session token, which is shared across different instances, and there is no way to turn this off.

You could maybe work around this by manually logging out and logging in as a guest, but I’d discourage this.

I’ll make a ticket about this to discuss it internally, but my main advice right now would be to test using different Unity editor instances with something like ParrelSync, instead of trying to use different instances of the same installation.

---

<div class="post-metadata">

**Author:** ![Kevin](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/kevin/32/410_2.png) [@Kevin](https://community.coherence.io/u/Kevin)\
**Post date:** [March 29, 2024, 6:22pm UTC](https://community.coherence.io/t/multiple-clients-each-using-loginasguest-locally-share-the-same-account/480/3 "2024-03-29T18:22:16Z")

</div>

Thanks for the reply @miguel-coherence .

As you suggested, what I had originally done is detect this error and run the lgout flow, then automatically push the client back through the login flow. Seems to be working fine for my limited testing currently, but I’m not really using the accounts right now, I just need them to connect to the cloud services in each client. Will have to see how it holds up, but happy to explore other options later on if they are available.

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex017/uploads/coherence/original/1X/b3aa79eb9519fac7aad7eba18f15a1e8ce60f6e2.png) [@system](https://community.coherence.io/u/system)\
**Post date:** [June 27, 2024, 6:22pm UTC](https://community.coherence.io/t/multiple-clients-each-using-loginasguest-locally-share-the-same-account/480/4 "2024-06-27T18:22:44Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.