You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a working LDAP groups mapping, that works on CRON and correctly adds new users to gitea org groups. But the configuration "Remove users from synchronized teams if user belongs to corresponding LDAP group" seems not to work correctly, as i still see a deleted user from LDAP after gitea source sync.
Also, there is lack of documentation, that describes how to configure correctly ldap group mappings and what does each config means
As a backend we have a FreeIPA
Gitea Version
1.23.1
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
Linux Ubuntu 22.04
How are you running Gitea?
Docker
Database
PostgreSQL
The text was updated successfully, but these errors were encountered:
Description
We have a working LDAP groups mapping, that works on CRON and correctly adds new users to gitea org groups. But the configuration "Remove users from synchronized teams if user belongs to corresponding LDAP group" seems not to work correctly, as i still see a deleted user from LDAP after gitea source sync.
Also, there is lack of documentation, that describes how to configure correctly ldap group mappings and what does each config means
As a backend we have a FreeIPA
![Image](https://private-user-images.githubusercontent.com/15741789/409167837-d4c640c3-68c1-4476-8cc9-f6fcb26c62e9.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyNzkyOTIsIm5iZiI6MTczOTI3ODk5MiwicGF0aCI6Ii8xNTc0MTc4OS80MDkxNjc4MzctZDRjNjQwYzMtNjhjMS00NDc2LThjYzktZjZmY2IyNmM2MmU5LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjExVDEzMDMxMlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTY0YjBmNjJkMWQ1MDAzNDQ4Yjc4MTBmZDgzMDhhZmIwY2YyMzFmMGUzYTNhNGEzZDIyNDNkYTY1MTdmNzQ3ZDgmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.fvdg8j-7jNiCiE4QiL-H0ROh7Ss72ZvQAGezkYNrkAY)
![Image](https://private-user-images.githubusercontent.com/15741789/409167835-04b5af1a-1be7-4fb8-9121-edc0f3e570c2.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyNzkyOTIsIm5iZiI6MTczOTI3ODk5MiwicGF0aCI6Ii8xNTc0MTc4OS80MDkxNjc4MzUtMDRiNWFmMWEtMWJlNy00ZmI4LTkxMjEtZWRjMGYzZTU3MGMyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjExVDEzMDMxMlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTQ3M2FjYzc5NzBlZDk4OGFkZTc4ZjUzNmI3ZDY3ZTU3YzlkOGE2OTZmZTAzZWUyOTc2YjRlYmQ2NDU4NmM5MzcmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.fUPrkjPR_Uvgr7l97BwbVmwzXkbMEZZGh0qDCsjAtY4)
![Image](https://private-user-images.githubusercontent.com/15741789/409167836-779a8e3b-5c3d-4df6-bd88-6f4b3daddac2.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyNzkyOTIsIm5iZiI6MTczOTI3ODk5MiwicGF0aCI6Ii8xNTc0MTc4OS80MDkxNjc4MzYtNzc5YThlM2ItNWMzZC00ZGY2LWJkODgtNmY0YjNkYWRkYWMyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjExVDEzMDMxMlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTA5MmE3M2VlNzZhOWY5ZjQ2NWE0OWNkNzJlMTBhNmI1NjNmNzE3MTA4NjQ1ZjdlZTk0Yjc1Y2E4ZWFlZjZlNjcmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.eAGkzJoYfFkvaZkXvE2InJUNgFEkPGrDvWtkapdjXZw)
Gitea Version
1.23.1
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
Linux Ubuntu 22.04
How are you running Gitea?
Docker
Database
PostgreSQL
The text was updated successfully, but these errors were encountered: