dump bug in converstion of authentications #1027

Closed
opened 2025-11-02 03:45:49 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @ghost on GitHub (Aug 30, 2017).

Gitea Version: 1.2.0+rc1

  • Database
    was sqlite
    dump and moved to mariadb

  • Can you reproduce the bug:

    • [x ] Yes

./gitea dump -d mysql
-load the resulting sql file to mariadb
-modify app.ini to use mysql
-cannot login with external authentication any longer
-login with local admin account and see problem

original authentication before conversion
(&(groupMembership=cn=it,ou=UserGroups,ou=Unix,ou=Groups,ou=a,ou=b,o=c)(cn=%s))
after conversion
(u0026(groupMembership=cn=it,ou=UserGroups,ou=Unix,ou=Groups,ou=a,ou=b,o=c)(cn=%s))

the ampersand was changed to unicode.

Originally created by @ghost on GitHub (Aug 30, 2017). Gitea Version: 1.2.0+rc1 - Database was sqlite dump and moved to mariadb - Can you reproduce the bug: - [x ] Yes ./gitea dump -d mysql -load the resulting sql file to mariadb -modify app.ini to use mysql -cannot login with external authentication any longer -login with local admin account and see problem original authentication before conversion (&(groupMembership=cn=it,ou=UserGroups,ou=Unix,ou=Groups,ou=a,ou=b,o=c)(cn=%s)) after conversion (u0026(groupMembership=cn=it,ou=UserGroups,ou=Unix,ou=Groups,ou=a,ou=b,o=c)(cn=%s)) the ampersand was changed to unicode.
GiteaMirror added the issue/staletype/bug labels 2025-11-02 03:45:49 -06:00
Author
Owner

@bkcsoft commented on GitHub (Sep 11, 2017):

I'm not sure that Gitea supports migrations between different SQL dialects :/

@bkcsoft commented on GitHub (Sep 11, 2017): I'm not sure that Gitea supports migrations between different SQL dialects :/
Author
Owner

@stale[bot] commented on GitHub (Feb 12, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 12, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
Author
Owner

@stale[bot] commented on GitHub (Feb 26, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Feb 26, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1027