# LDAP vs. READ Permissons

**URL:** <https://community.cloudogu.com/t/ldap-vs-read-permissons/998>\
**Category:** SCM-Manager (General)\
**Created:** [December 5, 2022, 3:05pm UTC](https://community.cloudogu.com/t/ldap-vs-read-permissons/998 "2022-12-05T15:05:54Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![christian.pommer](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/christian.pommer/32/830_2.png) [@christian.pommer](https://community.cloudogu.com/u/christian.pommer)\
**Post date:** [December 5, 2022, 3:05pm UTC](https://community.cloudogu.com/t/ldap-vs-read-permissons/998/1 "2022-12-05T15:05:54Z")

</div>

Hello,  
all users of my SCM Manager installation can view all repositories on the server. The rights to each repository are only with the creators, but still everyone can see them. My SCM is connected to LDAP.  
Where could be my error.  
Thanks a lot!  
Christian

---

<div class="post-metadata">

**Author:** ![eheimbuch](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/eheimbuch/32/18_2.png) [@eheimbuch](https://community.cloudogu.com/u/eheimbuch)\
**Post date:** [December 5, 2022, 6:19pm UTC](https://community.cloudogu.com/t/ldap-vs-read-permissons/998/2 "2022-12-05T18:19:24Z")

</div>

Hey Christian,

it sounds like all users have a group which is permitted to read all repositories. I would check the group `_authenticated` first. 🙂

Edit: If you use anonymous access for SCM-Manager and the anonymous user account is permitted to see all repositories, all users could see your repositories without even be logged in.

Regards, Eduard

---

<div class="post-metadata">

**Author:** ![christian.pommer](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/christian.pommer/32/830_2.png) [@christian.pommer](https://community.cloudogu.com/u/christian.pommer)\
**Post date:** [December 6, 2022, 8:16am UTC](https://community.cloudogu.com/t/ldap-vs-read-permissons/998/3 "2022-12-06T08:16:40Z")

</div>

Dear Eduard,  
thank you very much for your answer.  
I have checked the SCM Anonymous. All permissions are disabled - no check mark.  
The users of the \_authenticated group are only allowed to create, archive and export repositories.  
Thanks and greetings  
Christian

---

<div class="post-metadata">

**Author:** ![eheimbuch](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/eheimbuch/32/18_2.png) [@eheimbuch](https://community.cloudogu.com/u/eheimbuch)\
**Post date:** [December 6, 2022, 8:41am UTC](https://community.cloudogu.com/t/ldap-vs-read-permissons/998/4 "2022-12-06T08:41:33Z")

</div>

Okay, you could also check:

- Is there any group with “read all repositories” permission? Is anonymous user included?
- Is this permission set on namespace level? Maybe for a group?

Besides direct permissions there are also “permission roles” which may allow to be `read`, `write` or `owner` for your repositories.

---

<div class="post-metadata">

**Author:** ![christian.pommer](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/christian.pommer/32/830_2.png) [@christian.pommer](https://community.cloudogu.com/u/christian.pommer)\
**Post date:** [December 6, 2022, 10:04am UTC](https://community.cloudogu.com/t/ldap-vs-read-permissons/998/5 "2022-12-06T10:04:21Z")

</div>

I have only one group, called \_authenticated. The checkmark is set at “Members of this group are managed by an external system”. The group is only authorized to create, archive or export repositories.  
Where can I check “permission set on namespace level”?  
Thanks a lot for your help!

---

<div class="post-metadata">

**Author:** ![eheimbuch](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/eheimbuch/32/18_2.png) [@eheimbuch](https://community.cloudogu.com/u/eheimbuch)\
**Post date:** [December 6, 2022, 12:13pm UTC](https://community.cloudogu.com/t/ldap-vs-read-permissons/998/6 "2022-12-06T12:13:57Z")

</div>

![Screenshot from 2022-12-06 13-12-10](https://europe1.discourse-cdn.com/flex013/uploads/cloudogu2/original/1X/762456676d8a65006dc151da8467962f1acdfa4a.png)

Click this blue gear wheel on top of your repository namespace on your overview. But if you didn’t know about this it should be pretty unlikely. 🤔

---

<div class="post-metadata">

**Author:** ![christian.pommer](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/christian.pommer/32/830_2.png) [@christian.pommer](https://community.cloudogu.com/u/christian.pommer)\
**Post date:** [December 6, 2022, 1:26pm UTC](https://community.cloudogu.com/t/ldap-vs-read-permissons/998/7 "2022-12-06T13:26:24Z")

</div>

Sorry I was just confused, I know of course they are namespaces. Permissions in all namespaces are empty. There are no group or user permissions transactions.

---

<div class="post-metadata">

**Author:** ![christian.pommer](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/christian.pommer/32/830_2.png) [@christian.pommer](https://community.cloudogu.com/u/christian.pommer)\
**Post date:** [December 7, 2022, 1:47pm UTC](https://community.cloudogu.com/t/ldap-vs-read-permissons/998/8 "2022-12-07T13:47:14Z")

</div>

I was able to solve the problem. The group \_authenticated must only have the right to create repositories. As soon as you give it the right to export or archive, every user of this group can also see all repositories. But this was not the case before one of the last updates. I think this is a bug.

---

<div class="post-metadata">

**Author:** ![eheimbuch](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/eheimbuch/32/18_2.png) [@eheimbuch](https://community.cloudogu.com/u/eheimbuch)\
**Post date:** [December 7, 2022, 7:08pm UTC](https://community.cloudogu.com/t/ldap-vs-read-permissons/998/9 "2022-12-07T19:08:48Z")

</div>

Thank you for the report. We will discuss this and look for a solution.
