nextcloud / nextcloud/talk-desktop

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

Open
#1,471 4 comments 2 reactions 1 assignee View on GitHub

@ShGKme is already working on this.

Since Oct 2, 2025.

bug
Dominant language
JavaScript
Stars
525
Forks
85
Avg merge
8h 5m
Merged PRs (30d)
35

Description

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": []
}

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.