[GH-ISSUE #218] Centralize accounts in settings #3074

Closed
opened 2026-03-13 01:35:21 +03:00 by kerem · 3 comments
Owner

Originally created by @coooly on GitHub (Mar 16, 2022).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/218

Originally assigned to: @VShawn on GitHub.

Hello !
Could it be possible to centralize accounts in settings ?

Main value will be able to change an account password in one location instead of every connection using it.

Thank you

Originally created by @coooly on GitHub (Mar 16, 2022). Original GitHub issue: https://github.com/1Remote/1Remote/issues/218 Originally assigned to: @VShawn on GitHub. Hello ! Could it be possible to centralize accounts in settings ? Main value will be able to change an account password in one location instead of every connection using it. Thank you
kerem 2026-03-13 01:35:21 +03:00
Author
Owner

@majkinetor commented on GitHub (Mar 16, 2022):

No, its not possible.
There is easy alternative - you can bulk edit credential by selecting multiple connections.

The only benefit of centralized editing is that you don't need to select connections which is really minor thing and you could tag all those connections easily if you want later to be able to select this group with one click.

Furthermore, if you really have lots and lots of connections and you can't find them easily, you can use sqlite query to find them since db is sqlite and can be queried trivially with something like this:

select json_extract(JsonConfigString, '$.UserName') as UserName 
from Server
where UserName = 'root'

This sql searches for root (I used FOSS tool dbeaver to execute this on premotem.db). With it, you can set username directly via SQL or add unique tag that you can later use to not mess with SQL and do bulk edit directly.

Maybe we could enhance search via more keywoards to allow for this without SQL (/cc @VShawn). Currently we can search for tags with #xyz, but maybe something like username: xyx could be added eventually so less adventurous folks don't have to use SQL for huge number of connections.

<!-- gh-comment-id:1069302564 --> @majkinetor commented on GitHub (Mar 16, 2022): No, its not possible. There is easy alternative - you can bulk edit credential by selecting multiple connections. The only benefit of centralized editing is that you don't need to select connections which is really minor thing and you could tag all those connections easily if you want later to be able to select this group with one click. Furthermore, if you really have lots and lots of connections and you can't find them easily, you can use sqlite query to find them since db is sqlite and can be queried trivially with something like this: ```sql select json_extract(JsonConfigString, '$.UserName') as UserName from Server where UserName = 'root' ``` This sql searches for root (I used FOSS tool [dbeaver](https://dbeaver.io/) to execute this on `premotem.db`). With it, you can set username directly via SQL or add unique tag that you can later use to not mess with SQL and do bulk edit directly. Maybe we could enhance search via more keywoards to allow for this without SQL (/cc @VShawn). Currently we can search for tags with `#xyz`, but maybe something like `username: xyx` could be added eventually so less adventurous folks don't have to use SQL for huge number of connections.
Author
Owner

@majkinetor commented on GitHub (Mar 16, 2022):

Duplicate: https://github.com/VShawn/PRemoteM/issues/89

<!-- gh-comment-id:1069303086 --> @majkinetor commented on GitHub (Mar 16, 2022): Duplicate: https://github.com/VShawn/PRemoteM/issues/89
Author
Owner

@coooly commented on GitHub (Mar 16, 2022):

Thank you. With a tag and bulk editing I can achieve easily what I was looking for. 😊

<!-- gh-comment-id:1069334756 --> @coooly commented on GitHub (Mar 16, 2022): Thank you. With a tag and bulk editing I can achieve easily what I was looking for. 😊
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/1Remote#3074
No description provided.