# Select database on web client using URL

**URL:** https://discuss.tryton.org/t/select-database-on-web-client-using-url/7536
**Category:** User
**Tags:** web-user
**Created:** [August 10, 2024, 3:56pm UTC](https://discuss.tryton.org/t/select-database-on-web-client-using-url/7536 "2024-08-10T15:56:35Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![rvong](https://discuss-cdn.tryton.org/letter_avatar_proxy/v4/letter/r/3bc359/32.png) [@rvong](https://discuss.tryton.org/u/rvong)
#### Post date: [August 10, 2024, 3:56pm UTC](https://discuss.tryton.org/t/select-database-on-web-client-using-url/7536/1 "2024-08-10T15:56:35Z")

</div>

When there are multiple separate databases being served from the same Trytond server we normally select the database we want to connect from the login dialog of the web client. However this leaks information about the existence of the many databases available to anyone using the web client.

One way to solve this problem is to disable the database listing by adding `list = False` in the server config. However this brings an inconvenience to the user that he/she needs to type in the database name in the login dialog field every time. So I was wondering if there is a way one can specify or “pre-select” the database to connect by adding this as a parameter in the URL loading the web-client?

I tried something like `http://localhost:8080/#demo70` or `http://localhost:8080/?database=demo70` and both still requires user type in the database name. If this is not implemented yet, I wonder if this is a feature we could add to the SAO client?

---

<div class="post-metadata">

### Author: ![ced](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/ced/32/1237_2.png) [@ced](https://discuss.tryton.org/u/ced)
#### Post date: [August 11, 2024, 12:55am UTC](https://discuss.tryton.org/t/select-database-on-web-client-using-url/7536/2 "2024-08-11T00:55:18Z")

</div>

> [@rvong](#):
>
> like `http://localhost:8080/#demo70`

Normally this should be working.  
But maybe it is not if the database listing is disable. In such case I see no argument against making it works.
