Can you explain the relationship. I do not think I follow. What is in each container? SSSD? If SSSD is in a continer there should not be any other containers inside that same container.

Replying to [comment:1 dpal]:

Can you explain the relationship. I do not think I follow. What is in each container? SSSD? If SSSD is in a continer there should not be any other containers inside that same container.

Dmitri, here we are talking about LDB's container object class and not about OS containers.
When using secrets, the protocol requires a user to create this container to store an entry in it. But this container may also have another containers stored in it and that's what the bug is about.

Please, Simo, feel free to correct me in case I got something wrong.

Sorry for confusion. Container is a loaded term nowadays. I get it now.

Fields changed

owner: somebody => fidencio

From a conversation on #sssd:

09:23 <fidencio> simo: hey/morning/afternoon! I'm taking care of that bugs I opened for secrets about depth limit and quota. do you have some suggestion about what could be reasonable default value for those options?

10:14 <simo> for depth limit I would say maybe 4

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.15 Beta

Fields changed

rhbz: => todo

Fields changed

patch: 0 => 1
status: new => assigned

• master: efc65e7

milestone: SSSD 1.15 Beta => SSSD 1.14.2

Fields changed

resolution: => fixed
status: assigned => closed

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/4201

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.