summaryrefslogtreecommitdiff
path: root/testprogs/ejs/minschema.js
AgeCommit message (Collapse)AuthorFilesLines
2007-10-10r11467: yay! mmc now accepts our schema. The trick was to get all the OIDAndrew Tridgell1-0/+14
mappings right for the attributeTypes field of the aggregate schema now to add the display specifiers and I won't need the proxy module any more (This used to be commit 69264362bd408f493487482a8d5e9779d9a0d475)
2007-10-10r11463: more progress on the schema generator. mmc now accepts all partsAndrew Tridgell1-3/+23
except the attributeTypes fields of the Aggregrate record. Proxying just that field and the display specifiers gives us a working mmc client hopefully i'll work out what it doesn't like about the attributeTypes field soon (This used to be commit 3af867a3f4a5fd702089400d1687e2aff017f48a)
2007-10-10r11436: this is work in progress for generating the schema we need for our ADSAndrew Tridgell1-18/+507
ldap server. It's still not quite right, and I'm chasing down a few errors that mmc throws up, but its a lot closer than it was. I had to change the approach quite substantially over the last couple of days, but this approach now seems to be working out. (This used to be commit 38ea11510c8824285d072fe0e03e443d9d584271)
2007-10-10r10990: the beginnings of a program designed to work out the minimal schemaAndrew Tridgell1-0/+112
needed to represent all the current records on a ADS LDAP server. The idea is we will use something based on this code to work out exactly what schema elements we will need for our initial ADS schema. I plan on expanding this code to automatically work out attribute properties, and write out a schema file that we can load into ldb. Interestingly, it looks like we only need 43 objectclasses and around 200 attributes to represent all records of a newly installed w2k3 ADS server. (This used to be commit 7b0ae77757d347d2b0f5bac3a49e915e24c3ab78)