#119 App access tokens

Closed
opened 1 month ago by 6543 · 5 comments
6543 commented 1 month ago

If you log on and off multible times, for example to switch betwen instances or for testing ...

each logon a new token is created instead of using the old one or delete the old one ...

If you log on and off multible times, for example to switch betwen instances or for testing ... each logon a new token is created instead of using the old one or delete the old one ... ![](https://cloud.obermui.de/apps/gallery/preview.public/1475266?width=2000&height=2000&c=69d4f04a14d835cb06a5e59abd6fcf13&requesttoken=4d%2B4vsboMCbjaZPhXl35u%2FcKrtug7DhRlf1%2FzM9j7%2BU%3D%3AqrjZ%2Bo6cZmW7EfatLTqPg7ln4bzapGIJxYcdnuQHl4A%3D&token=dDTcCcrJfGy3KcK)
6543 added this to the 2.3.0 milestone 1 month ago
6543 added the
Refactor
label 1 month ago
6543 closed this issue 1 month ago
mmarif was assigned by 6543 1 month ago
mmarif commented 1 month ago
Owner

Each login will not create new token but each new installation will.

Also there are times when the app can be used in multiple devices, so it’s risky to delete other tokens.

But I am open to ideas on this.

Each login will not create new token but each new installation will. Also there are times when the app can be used in multiple devices, so it's risky to delete other tokens. But I am open to ideas on this.
6543 commented 1 month ago
Poster

I’ll leave it for later
when multi instance function is implemented we can look at this again?

I'll leave it for later when multi instance function is implemented we can look at this again?
mmarif commented 1 month ago
Owner

Yes, we can leave it for later.

Actually before implementing this, I thought many times and considered many scenarios for deleting tokens. But then I dropped that idea for many other reasons(like one above).

Yes, we can leave it for later. Actually before implementing this, I thought many times and considered many scenarios for deleting tokens. But then I dropped that idea for many other reasons(like one above).
mmarif commented 1 month ago
Owner

It’s time to revisit this issue after merging #179 .

I feel a clean refactor is needed to reduce the tokens created.

It's time to revisit this issue after merging #179 . I feel a clean refactor is needed to reduce the tokens created.
mmarif commented 1 month ago
Owner

Closed via #202

Closed via #202
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.