-
-
Notifications
You must be signed in to change notification settings - Fork 318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error Data too long when authenticating via Gitea OAuth #516
Comments
Problem originates from table CREATE TABLE `oauth_users` (
`user_id` int(11) NOT NULL,
`remote_user_id` varchar(128) NOT NULL,
`provider` varchar(24) NOT NULL DEFAULT '',
`client_id` varchar(128) NOT NULL DEFAULT '',
`access_token` varchar(512) NOT NULL DEFAULT '',
UNIQUE KEY `oauth_users_uk` (`user_id`,`provider`,`client_id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 Notice This query fixes the problem: ALTER TABLE `oauth_users`
MODIFY `access_token`
varchar(1024); What would be the best way to include this statement into migrations? |
Thanks for reporting this, @gytisrepecka! To add this migration, you can follow the example of this commit: 5de4d20 |
Thanks, I will create a Pull Request. Or shall I perhaps use |
Thanks for raising this, ran into it too integrating with Keycloak! Good to see a fix coming down the tubes ❤️ |
@gytisrepecka if you're creating a PR, could you make the column 2048 chars long? Keycloak gives very long auth tokens (>1300 bytes). Thanks! |
Since it's |
With authentik there is also the problem, there I had to increase the size to 2048 |
This should be fixed with #618, which will be in the next release. |
Describe the bug
Following error is returned when loggin in via Gitea:
Steps to reproduce
Steps to reproduce the behavior:
Expected behavior
Should successfully login.
Application configuration
Version or last commit: v0.13.1
The text was updated successfully, but these errors were encountered: