OpenID 500 Error from AliCloud OAuth Integration #4680

New Issue

GiteaMirror · 2025-11-02T05:59:16-06:00

GiteaMirror commented

2025-11-02 05:59:16 -06:00

Originally created by @caryyu on GitHub (Jan 19, 2020).

Gitea version (or commit ref): eb0ee6b
Git version: Forgot
Operating system: Linux
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (https://help.aliyun.com/document_detail/69964.html - Chinese only)
- No
- Not relevant
Log gist: No Need

Description

You can just register an ali-cloud account and use its RAM oauth2 feature, then you will find out the integration won't work

I assume the issue is because Alicloud userdetail doesn't fit the standard user claims return

Screenshots

Originally created by @caryyu on GitHub (Jan 19, 2020).   - Gitea version (or commit ref): eb0ee6b - Git version: Forgot - Operating system: Linux - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (https://help.aliyun.com/document_detail/69964.html - Chinese only) - [ ] No - [ ] Not relevant - Log gist: No Need ## Description You can just register an ali-cloud account and use its RAM oauth2 feature, then you will find out the integration won't work > I assume the issue is because Alicloud userdetail doesn't fit the standard user claims return ## Screenshots ![image](https://user-images.githubusercontent.com/4496641/72673533-cc03ba80-3aa6-11ea-9877-4de9b6855caa.png)

GiteaMirror added the type/question label 2025-11-02 05:59:16 -06:00

GiteaMirror closed this issue

2025-11-02 05:59:16 -06:00

GiteaMirror commented

2025-11-02 05:59:17 -06:00

@techknowlogick commented on GitHub (Jan 19, 2020):

Do you use https://oauth.aliyun.com/.well-known/openid-configuration as your OpenID connect URL? Any logs you can provide that show what the trace of error is?

@techknowlogick commented on GitHub (Jan 19, 2020): Do you use https://oauth.aliyun.com/.well-known/openid-configuration as your OpenID connect URL? Any logs you can provide that show what the trace of error is?

GiteaMirror commented

2025-11-02 05:59:17 -06:00

@caryyu commented on GitHub (Jan 19, 2020):

@techknowlogick Yeah, I did use https://oauth.aliyun.com/.well-known/openid-configuration in the auto-discovery field, in fact, at first when I click the log-in button, it definitely will redirect to Alicloud login page, however, after all the login-actions being done on the alicloud side, which will redirect back without any problems, and then in Gitea, this error came out, which I suspect the error is something relevant to OAuth2 userdetail-claims

@caryyu commented on GitHub (Jan 19, 2020): @techknowlogick Yeah, I did use https://oauth.aliyun.com/.well-known/openid-configuration in the auto-discovery field, in fact, at first when I click the log-in button, it definitely will redirect to Alicloud login page, however, after all the login-actions being done on the alicloud side, which will redirect back without any problems, and then in Gitea, this error came out, which I suspect the error is something relevant to OAuth2 userdetail-claims

GiteaMirror commented

2025-11-02 05:59:17 -06:00

@caryyu commented on GitHub (Jan 19, 2020):

@techknowlogick sorry, I don't know the log file where the trace error is, I will try that later today

@caryyu commented on GitHub (Jan 19, 2020): @techknowlogick sorry, I don't know the log file where the trace error is, I will try that later today

GiteaMirror commented

2025-11-02 05:59:18 -06:00

@caryyu commented on GitHub (Jan 20, 2020):

@techknowlogick From today's test, I face another issue which I don't know if it is normal behavior after logging-in via OpenID, very weird....:

@caryyu commented on GitHub (Jan 20, 2020): @techknowlogick From today's test, I face another issue which I don't know if it is normal behavior after logging-in via OpenID, very weird....: ![image](https://user-images.githubusercontent.com/4496641/72704026-63920780-3b92-11ea-9812-9e8bb2975f4a.png)

GiteaMirror commented

2025-11-02 05:59:18 -06:00

@techknowlogick commented on GitHub (Jan 21, 2020):

Ah ok. It's now working as expected. You need to link your alicloud account to a gitea account.

Looking at your screenshot you are using a really old version of gitea (1.6.4), and I recommend you upgrade to the latest 1.10.3.

I will close this as oidc is working as expected with alicloud.

@techknowlogick commented on GitHub (Jan 21, 2020): Ah ok. It's now working as expected. You need to link your alicloud account to a gitea account. Looking at your screenshot you are using a really old version of gitea (1.6.4), and I recommend you upgrade to the latest 1.10.3. I will close this as oidc is working as expected with alicloud.

GiteaMirror commented

2025-11-02 05:59:18 -06:00

@caryyu commented on GitHub (Jan 21, 2020):

@techknowlogick Any way that I can prevent second registration if SSO has been enabled like this case, cuz the latest version I tried with alicloud will still ask me for a username and email sign-up, Ideally, we can preset both email and username from OAuth2 user details to avoid this second action to implement more reasonable SSO

@caryyu commented on GitHub (Jan 21, 2020): @techknowlogick Any way that I can prevent second registration if SSO has been enabled like this case, cuz the latest version I tried with alicloud will still ask me for a username and email sign-up, Ideally, we can preset both email and username from OAuth2 user details to avoid this second action to implement more reasonable SSO

GiteaMirror commented

2025-11-02 05:59:18 -06:00

@techknowlogick commented on GitHub (Jan 21, 2020):

@caryyu the functionality you are looking at exists in a more recent version and so I recommend upgrading.

@techknowlogick commented on GitHub (Jan 21, 2020): @caryyu the functionality you are looking at exists in a more recent version and so I recommend upgrading.

GiteaMirror commented

2025-11-02 05:59:19 -06:00

@caryyu commented on GitHub (Jan 22, 2020):

@techknowlogick would you mind sharing a little reference about here, which can simply be a commit link or anything else equivalent, thanks a lot.

@caryyu commented on GitHub (Jan 22, 2020): @techknowlogick would you mind sharing a little reference about here, which can simply be a commit link or anything else equivalent, thanks a lot.

GiteaMirror commented

2025-11-02 05:59:19 -06:00

@techknowlogick commented on GitHub (Jan 22, 2020):

I believe the following ticket #5006 enhances the flow. However version 1.6.4 that you are on has security issues, and so you should update to latest stable (1.10.3) regardless.

For more questions please join us in chat https://discord.gg/gitea or on our forum https://discourse.gitea.io/ and we'd be happy to help there.

@techknowlogick commented on GitHub (Jan 22, 2020): I believe the following ticket [#5006](https://togithub.com/go-gitea/gitea/pull/5006) enhances the flow. However version 1.6.4 that you are on has security issues, and so you should update to latest stable (1.10.3) regardless. For more questions please join us in chat https://discord.gg/gitea or on our forum https://discourse.gitea.io/ and we'd be happy to help there.

GiteaMirror referenced this issue

2025-11-02 13:32:14 -06:00

[PR #4680] [MERGED] Hide org/create menu item in Dashboard if user has no rights (#4678) #17460

GiteaMirror referenced this issue

2025-11-02 13:33:11 -06:00

[PR #4686] [MERGED] Backport: Hide org/create menu item in Dashboard if user has no rights (#4678) #17464

Sign in to join this conversation.