Giter Club home page Giter Club logo

Comments (5)

or-else avatar or-else commented on May 23, 2024

Hi Riandy,

FCM token refresh in the middle of user session

Yes, it's an oversight. This functionality is needed but missing. I see two options: allow {hi} in the middle of the session or create a new packet for the purpose, like {dev}. Let me look at the code and I'll suggest which one is more suitable.

User logout in app

So, if I understand correctly, when user logs out from the device, the app needs a way to tell the server to invalidate the token. But maybe it's not needed. Since tokens are stored by UID, if the same token is used with a new UID the server can detect that and then invalidate the token for the old UID. I think the automatic token invalidation is better than explicit because it will not allow a malicious client to intentionally receive pushes for a different user. If you don't see problems with this approach, I'll add automatic token deletion on the server.

Also if I may suggest I think it's better if we differentiate between deviceId & fcm token though. The reason is because essentialy a device may have multiple tokens due to rotation / refresh.

But what is deviceId then? I don't think there is a need for a deviceId separate from the push token. Just think of deviceId as a different name for the token.
As for stale deviceId (or token), I think it needs garbage collection - automatically delete deviceId/token after a month of two of inactivity.

from chat.

riandyrn avatar riandyrn commented on May 23, 2024

I think the automatic token invalidation is better than explicit because it will not allow a malicious client to intentionally receive pushes for a different user.

Yeah, you’re right it’s much better (y).

Maybe the trade off is when user already logged out then move to new device, they would still receive the notification in the old device. Maybe you have suggestion regarding this case?

But what is deviceId then?

I was thinking to use InstanceID

from chat.

or-else avatar or-else commented on May 23, 2024

Maybe the trade off is when user already logged out then move to new device, they would still receive the notification in the old device. Maybe you have suggestion regarding this case?

I'm thinking about adding a way of updating the token which should cover both cases:

  1. Replace old token with the new token
  2. Replace token with null

I was thinking to use InstanceID

It's not going to be used on the backend so I would rather not collect it.

from chat.

or-else avatar or-else commented on May 23, 2024

I think allowing {hi} in the middle of a session is the simplest solution: #51

from chat.

riandyrn avatar riandyrn commented on May 23, 2024

Hello, Gene

Yeah, it’s awesome 👍

I have a little bit fix for null params in {hi} response though: #55

Thanks

from chat.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.