Cannot change custom OAuth2 Nextcloud URL #5607

Closed
opened 2025-11-02 06:30:40 -06:00 by GiteaMirror · 5 comments
Owner

Originally created by @SohnyBohny on GitHub (Jun 22, 2020).

  • Gitea version (or commit ref):
  • Git version:
  • Operating system:
  • Database (use [x]):
    • MySQL
  • Can you reproduce the bug at https://try.gitea.io:
    • No (admin)
  • Log gist:

Description

Cannot change custom OAuth2 Nextcloud URL default entries.

Screenshots

Screen Capture

Originally created by @SohnyBohny on GitHub (Jun 22, 2020). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): - Git version: - Operating system: - Database (use `[x]`): - [x] MySQL - Can you reproduce the bug at https://try.gitea.io: - [x] No (admin) - Log gist: ## Description Cannot change custom OAuth2 Nextcloud URL default entries. ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** --> ![Screen Capture](https://user-images.githubusercontent.com/10254103/85291004-3677b700-b49a-11ea-8057-b449f13e2703.gif)
GiteaMirror added the type/bug label 2025-11-02 06:30:40 -06:00
Author
Owner

@SohnyBohny commented on GitHub (Jun 23, 2020):

Small update: It's only a UI problem. Internally the changes are applied.

@SohnyBohny commented on GitHub (Jun 23, 2020): Small update: It's only a UI problem. Internally the changes are applied.
Author
Owner

@stale[bot] commented on GitHub (Aug 23, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Aug 23, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.
Author
Owner

@SohnyBohny commented on GitHub (Aug 24, 2020):

For me the problem still exists. Maybe someone else could test an confirm this bug.

@SohnyBohny commented on GitHub (Aug 24, 2020): For me the problem still exists. Maybe someone else could test an confirm this bug.
Author
Owner

@dugite-code commented on GitHub (Aug 27, 2020):

I was just setting this up and I see it as well. This is an issue as if you update the CLIENT ID or Secret without re-typing the correct domain it will overwrite your valid url

Gitea: Docker 1.13.0+dev-418-gd285b5d35
DB: sqlite

@dugite-code commented on GitHub (Aug 27, 2020): I was just setting this up and I see it as well. This is an issue as if you update the CLIENT ID or Secret without re-typing the correct domain it will overwrite your valid url Gitea: Docker 1.13.0+dev-418-gd285b5d35 DB: sqlite
Author
Owner

@nuno-silva commented on GitHub (Oct 13, 2020):

I'm seeing this issue as of gitea 1.12.4 using the Gitea auth source. The the fields are updated internally and are correct in the /admin/auths/<id> page response, but then it seems the java-script resets them to the default values. If I disable java-script I can see the correct endpoint values in the UI.

@nuno-silva commented on GitHub (Oct 13, 2020): I'm seeing this issue as of gitea 1.12.4 using the Gitea auth source. The the fields are updated internally and are correct in the `/admin/auths/<id>` page response, but then it seems the java-script resets them to the default values. If I disable java-script I can see the correct endpoint values in the UI.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#5607