Skip to content

First system user created upon logging in via LDAP is not marked as admin #1206

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

Closed
strk opened this issue Mar 10, 2017 · 6 comments
Closed
Labels
issue/stale type/question Issue needs no code to be fixed, only a description on how to fix it yourself.

Comments

@strk
Copy link
Member

strk commented Mar 10, 2017

Version 1.1.0.
Start with an empty database, configure usage of LDAP.
Login via LDAP results in automatic creation of local user record corresponding to the LDAP record, but even if that's the very first local user created, such user is not marked as administrator, which results in a system with no administrator users.

I'm not sure if this is a regression or not, didn't try with 1.0.x

@pgaskin
Copy link
Contributor

pgaskin commented Mar 10, 2017

I don't think it's a regression, I just tried it myself.

Also, can you review go-gitea/docs#99 and #1207 😄

@lunny
Copy link
Member

lunny commented Mar 11, 2017

How does first user login via LDAP?

@lunny lunny added the type/question Issue needs no code to be fixed, only a description on how to fix it yourself. label Mar 11, 2017
@strk
Copy link
Member Author

strk commented Mar 11, 2017

@lunny now this is a good question. In my case I created an admin user, added the loginSource then removed the admin user. But in general you're right that's currently not straightforward to enable LDAP w/out first creating an admin user. That's a problem addressed in #183

@lunny
Copy link
Member

lunny commented Mar 11, 2017

So delete the last user is a deny operation we should send a PR to do that.

@stale
Copy link

stale bot commented Feb 16, 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 stale bot added the issue/stale label Feb 16, 2019
@stale
Copy link

stale bot commented Mar 2, 2019

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

@stale stale bot closed this as completed Mar 2, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/stale type/question Issue needs no code to be fixed, only a description on how to fix it yourself.
Projects
None yet
Development

No branches or pull requests

3 participants