Change of ldap password lets Talk Desktop ask again for server url

[cm-schl]

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

---

Steps to reproduce

1. Use the LDAP integration to authenticate your users when accessing Nextcloud
2. Login the first time to Nextcloud Talk Desktop -> the user can use the program as intended
3. Change the LDAP password of the user account
4. Wait for some time, Nextcloud Talk Desktop will logout the user and ask for the server url

Expected behaviour

The user should not be asked for the server url as this information was already given to Talk Desktop at the first login. Talk Desktop should only ask for the new credentials.

Actual behaviour

User is asked to insert the server url.

Diagnosis and logs

Diagnosis report

Diagnosis report

Nextcloud Talk Desktop
Version	v1.2.6
Built-in Talk version	v21.1.4
Release channel	stable
Operating system	Windows_NT 10.0.26100 (Windows 11 Pro)
Executable Path	C:\Program Files\Nextcloud Talk\app-1.2.6\Nextcloud Talk.exe
Connected to	-
Nextcloud version	30.0.14
Nextcloud Talk version	20.1.9
notifications app enabled	✅ yes
notify_push app enabled	❌ no

Application config

{
  "launchAtStartup": true,
  "theme": "default",
  "systemTitleBar": false,
  "monochromeTrayIcon": false,
  "zoomFactor": 1,
  "playSoundChat": "respect-dnd",
  "playSoundCall": "respect-dnd",
  "enableCallbox": "respect-dnd",
  "secondarySpeaker": false,
  "secondarySpeakerDevice": null,
  "trustedFingerprints": []
}

[ShGKme]

Will be fixed via logging in via web-browser

[cm-schl]

Sorry maybe I understand your answer in the wrong way: will there be a modification to Talk Desktop that omits the question for the server url? We have users that only use Nextcloud Talk Desktop and therefore never log in via web-browser.

[ShGKme]

Sorry, I mixed it up with another issue... It has nothing to do with the login flow v2.

[ShGKme]

We'll add remembering the server URL.