bind-dyndb-ldap

Clone

#151 Implement internal meta-database
Closed: Fixed None Opened 9 years ago by pspacek.

Closed: Fixed
Reopen Issue

This is tracker for other tickets which can be implemented only if we store additional metadata somewhere.

It seems that easiest way how to proceed is to implement one central meta-database as additional layer on top of RBTDB and use it as key->value database.

this is meta-ticket

Metadata Update from @pspacek:
- Issue assigned to pspacek
- Issue set to the milestone: Fedora 22
7 years ago

Login to comment on this ticket.

Metadata
None
None
None
critical
0
None
70, 123, 124, 125, 126, 128
980d00c05d749d5a87ebf3b45e9ed222ac729626, b0b0fb542ed42d40e0ba3f8bae34f7fe9aa0a633, 0aa700bae38a5c653bb048b032cc785235591002, f1ca7432fe363a7175a9aa030ba3d9177863b0e0, 414f84d77372ef7d748d33047af0ea60d2282fe9, 472c1f2f739a793ea90044c9c35b32cae58d27d0, a6513c44d5576f94485630d5a0273c49f5c6c66e, 7e79bd6e90541131a21dc2a4784cd58abc7423e8, 9f64fe6f1d0860a201f6331b7996f76fcaf054fd, a14e1c4044cf6df5f4fc3198c119f877ddd37fc3, 35e79d6794ddf7a3a3472cfde07d983402be0f65, 5a203a3ecc49a4bbb6cd32fb2dc669c701c04030, e64dea627ff965149ca5dc2f5ed29c4307e229c4, ed82a73cbf9f087737073455d5e42c1cecbd4d11, 068538eacfe7b59e86d6712f83860584fa167787, b1a7bbab23e7b8669bb468094fe8faff104ebdd8, 32b5764969c64eac9c1783098ddddb35025e99ff, f83d99b6cdec9f89f624163996425f8c5eb9d018, d6071339f25e082373cf440f5c81a980e9459a64, dddb69ddbecec1b28109cc6d552a1643d6410c27, 808647cb1b35a4d8dbfe79b0c238509342780e36, 01ab6db5d0b002f4848446678930a3280742d211, 316ca66683d94345eb7db99499be7e58dc8f06ec, ffcc971fafbf50a0d65c8703e62584e3814064e3, 9ccc78af80661403a7c13df41d77cc8dd5658273, 37236dd1a4fe20b3e7254d12bb03498e5174e161
8.0
None
task
ldap driver
None
nihsyndrome
None
Powered by Pagure 5.13.3
Documentation • File an Issue • About • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.