Waarp Manager issueshttps://code.waarp.fr/apps/manager/manager/-/issues2024-03-25T14:32:52Zhttps://code.waarp.fr/apps/manager/manager/-/issues/442Get Gateway and Transfer version when refreshing the history2024-03-25T14:32:52ZBruno CarlinGet Gateway and Transfer version when refreshing the historyHaving the version of the app can be useful to generate their configuration or to enable some features (for example min version of gateway with support for FTP or PeSIT)Having the version of the app can be useful to generate their configuration or to enable some features (for example min version of gateway with support for FTP or PeSIT)0.18.3https://code.waarp.fr/apps/manager/manager/-/issues/441Add support for FTP interfaces for Gateway2024-02-26T15:48:34ZBruno CarlinAdd support for FTP interfaces for Gateway0.19.0https://code.waarp.fr/apps/manager/manager/-/issues/438Add forms to add PeSIT interfaces to Gateways2024-02-14T15:29:43ZBruno CarlinAdd forms to add PeSIT interfaces to Gateways0.19.0https://code.waarp.fr/apps/manager/manager/-/issues/437Add validations to the interfaces for the PeSIT protocol2024-02-14T15:28:09ZBruno CarlinAdd validations to the interfaces for the PeSIT protocol0.19.0https://code.waarp.fr/apps/manager/manager/-/issues/436Add PeSIT interface configuration to Gateway's JSON Files2024-02-14T15:29:11ZBruno CarlinAdd PeSIT interface configuration to Gateway's JSON Files0.19.0https://code.waarp.fr/apps/manager/manager/-/issues/435Add support for PeSIT Protocol in the next Gateway 0.92024-02-14T15:25:03ZBruno CarlinAdd support for PeSIT Protocol in the next Gateway 0.90.19.0Bruno CarlinBruno Carlinhttps://code.waarp.fr/apps/manager/manager/-/issues/430Use an internal R66 client instead of an external one2024-02-14T10:46:39ZBruno CarlinUse an internal R66 client instead of an external oneNote that when moving to an internal client using lib/r66>, the order and the needed rebounds (as given by the topology defined in sites and routes) must be kept.Note that when moving to an internal client using lib/r66>, the order and the needed rebounds (as given by the topology defined in sites and routes) must be kept.0.19.0Baptiste LeroyerBaptiste Leroyerhttps://code.waarp.fr/apps/manager/manager/-/issues/427Handle transferinfo forwarding2024-01-18T15:23:21ZBruno CarlinHandle transferinfo forwardingadd forwarding in default templates, possibly conditionallyadd forwarding in default templates, possibly conditionallynexthttps://code.waarp.fr/apps/manager/manager/-/issues/425Deactivate filewatcher tab if filewatcher config is not possible.2024-03-12T15:37:44ZMaxime Robertmaxime.robert@waarp.frDeactivate filewatcher tab if filewatcher config is not possible.Currently if no filewatcher can be setup for a flow the filewatcher tab is available but the button to activate it is disabled.
It would be better to deactivate the filewatcher tab to prevent user to access the filewatcher menuCurrently if no filewatcher can be setup for a flow the filewatcher tab is available but the button to activate it is disabled.
It would be better to deactivate the filewatcher tab to prevent user to access the filewatcher menu0.20.0https://code.waarp.fr/apps/manager/manager/-/issues/424Add a default group to LDAP authentification2024-03-12T15:37:44ZMaxime Robertmaxime.robert@waarp.frAdd a default group to LDAP authentificationIt should be to setup a default group to a LDAP authentification source.
All new user connecting from that source will be attributed to this group.
No group is a valid setup.It should be to setup a default group to a LDAP authentification source.
All new user connecting from that source will be attributed to this group.
No group is a valid setup.0.20.0https://code.waarp.fr/apps/manager/manager/-/issues/420Backend should validate that certificates is valid for the address that used it2024-03-12T15:37:43ZMaxime Robertmaxime.robert@waarp.frBackend should validate that certificates is valid for the address that used itCurrently it is possible to setup partner certificate in manager that are refused by gateway.
It should be easy to add a check to verify that the certificate has a SAN corresponding to the interface address.Currently it is possible to setup partner certificate in manager that are refused by gateway.
It should be easy to add a check to verify that the certificate has a SAN corresponding to the interface address.0.20.0https://code.waarp.fr/apps/manager/manager/-/issues/419An external partner and its linked gateway should be in the same site2024-03-12T15:37:44ZMaxime Robertmaxime.robert@waarp.frAn external partner and its linked gateway should be in the same siteCurrently an external partner in site A can be linked to a gateway in site B.
Limiting the linked gateway selection to the in-site gateway would ease the selection.
The enforcement should be done :
* frontend: in the dropdown list
* b...Currently an external partner in site A can be linked to a gateway in site B.
Limiting the linked gateway selection to the in-site gateway would ease the selection.
The enforcement should be done :
* frontend: in the dropdown list
* backend: in the before update/create
This should not break current installations where the partner and the linked gateway are in different site.0.20.0https://code.waarp.fr/apps/manager/manager/-/issues/416Add a field to set the IP address of a client interface2024-03-12T15:37:43ZBruno CarlinAdd a field to set the IP address of a client interfaceIt is useful for partners who check the origin IP of a client.
It should be optional.It is useful for partners who check the origin IP of a client.
It should be optional.0.20.0https://code.waarp.fr/apps/manager/manager/-/issues/410Partner Gateway creation does not work as it should2024-03-12T15:37:44ZMaxime Robertmaxime.robert@waarp.frPartner Gateway creation does not work as it should- [ ] <details><summary>Frontend: Fill the gateway form</summary>
- **HostID**
- **AES Key**
- Hostname
- **REST IP**
- **REST Port**
- **Temp REST Username**
- **Temp REST Password**
- ... Protocol parameters
</details>
...- [ ] <details><summary>Frontend: Fill the gateway form</summary>
- **HostID**
- **AES Key**
- Hostname
- **REST IP**
- **REST Port**
- **Temp REST Username**
- **Temp REST Password**
- ... Protocol parameters
</details>
- [ ] Frontend: Send the partner information to backend
- [ ] Backend check partner value
- [ ] Backend register partner
- [ ] Backend check partner value
- [ ] Backend register interfaces
If any of the above is in error creation fails
- [ ] Backend DB session is rollbacked
- [ ] Backend send error to frontend
- [ ] Frontend Print error on gateway form
Else
- [ ] Backend try to create monitoring user (monitoring_manager_ABCD:generated_password) on the gateway using Temp Rest information to authentify.
If Success
- [ ] Backend register new user (monitoring_manager_ABCD:generated_password)
- [ ] Backend send success to frontend
Else
- [ ] Backend send warning to frontend
- [ ] Frontend return to partner list0.20.0Maxime Robertmaxime.robert@waarp.frMaxime Robertmaxime.robert@waarp.frhttps://code.waarp.fr/apps/manager/manager/-/issues/406Paginate long lists in the backend rather than in the frontend2024-03-12T15:42:07ZBruno CarlinPaginate long lists in the backend rather than in the frontendCurrently, in Manager, all results are loaded by the frontend to speed up the display of each result page (pagination is done in the frontend.
For pages with huge results sets (transfer and flow history, audit), this can lead to huge pa...Currently, in Manager, all results are loaded by the frontend to speed up the display of each result page (pagination is done in the frontend.
For pages with huge results sets (transfer and flow history, audit), this can lead to huge pageload time and an increased pression on the backend and on the database to generate the result set.
To remediate that, pagination should be done server-side:
* New page parameters (in the url) should be added for the page to show, the sort column and the sort order
* On page load, only the results required by the parameters should be loaded by the frontend (i.e. what needs to be displayed). if the URL parameters are not given, default values should be used. the default value should be the same as they currently are.
* When the user changes the result page (by clicking prev or next, by entering a direct number, by changing the sort order of the results, or by changing one of the parameters in the URL), a new result set matching the parameters must be loaded from the backend and shown.
* Except when the requested change is initiated by changing directly the URL, the URL should be updated to match the new pagination parameters.0.19.0https://code.waarp.fr/apps/manager/manager/-/issues/374Adapt the config JSON to the new gateway clients2022-10-13T14:25:54ZBruno CarlinAdapt the config JSON to the new gateway clientsWaiting for apps/gateway/gateway#332Waiting for apps/gateway/gateway#332nexthttps://code.waarp.fr/apps/manager/manager/-/issues/334Show the fingerprint of keys and certs in the UI2023-01-09T11:57:57ZBruno CarlinShow the fingerprint of keys and certs in the UIWhether it is in the detailed view or in the edit form, a user has no feedback on whether a key/certificate is set or not.
This issue proposes to show a fingerprint on these screens so that the user knows there is something set.Whether it is in the detailed view or in the edit form, a user has no feedback on whether a key/certificate is set or not.
This issue proposes to show a fingerprint on these screens so that the user knows there is something set.nextDylan DinhDylan Dinhhttps://code.waarp.fr/apps/manager/manager/-/issues/333Enhance migration rollbacks2022-12-06T15:21:32ZBruno CarlinEnhance migration rollbacksTo Rollback the database to a previous version, a user must know its internal identifier. There is however no way to discover these ids.
This can be solved by adding:
1. aliasing the latest migration of a version to the name of that ver...To Rollback the database to a previous version, a user must know its internal identifier. There is however no way to discover these ids.
This can be solved by adding:
1. aliasing the latest migration of a version to the name of that version to ease migrations and rollbacks:
```sh
# Instead of
waarp-manager db migrate down 20220228
# do
waarp-manager db migrate down 0.15.0
# Instead of
waarp-manager db migrate up 20220423
# do
waarp-manager db migrate up 0.16.0
```
2. a `list` subcommand to `migrate` to list all known migrations. For example:
```sh
$ waarp-manager db migrate list
0.16.0 20220423 Does foo
20220301 Does bar
0.15.0 20220228 Does baz
[...]
```nexthttps://code.waarp.fr/apps/manager/manager/-/issues/301Cache the status of the partner during history refresh2022-06-08T14:47:34ZBruno CarlinCache the status of the partner during history refreshBruno CarlinBruno Carlinhttps://code.waarp.fr/apps/manager/manager/-/issues/300Get information on partners2022-06-08T14:47:34ZBruno CarlinGet information on partnersFor example: version, OSFor example: version, OSBruno CarlinBruno Carlin