How to design an LDAP schema?

I want to use a LDAP repository as login backend for a portal. Is there a sample schema I can use?

  • I want to switch Jenkins-CI from a local user db, for this I need to define user groups in the LDAP.

  • Answer:

    (Note, I'm not a heavy Jenkins users, but I'm hoping that this will at least be helpful...) Most systems either provide you a way to define which attributes in the schema one can use for username, pw, etc or expect to use one of the RFC standard schemas such as posixUser. Groups tend to be trickier, but there are essentially four ways in which applications tend to use/accept groups: groupOfUniqueNames nisNetgroups posixGroup individual DNs under some sort of container DN I believe in the case of Jenkins, it requires the user of filters for both username and group definitions.  Also see https://wiki.jenkins-ci.org/display/JENKINS/Standard+Security+Setup on some (sort of ridiculous, really) requirements around group naming.

Allen Wittenauer at Quora Visit the source

Was this solution helpful to you?

Other answers

You may want take a look at IETF's RFC 4519 and RFC 2307. Although RFC 4519 is for "LDAP user applications" and RFC 2307 for "LDAP as NIS", they offer attribute objectclass definitions and attribute syntax and matching rules that may help you with your own schema needs. Some LDAP implementations (e.g., IBM Tivoli Directory Server) include schema components that already define the objectclasses and attributes defined in these RFCs.

Bora Bali

Just Added Q & A:

Find solution

For every problem there is a solution! Proved by Solucija.

  • Got an issue and looking for advice?

  • Ask Solucija to search every corner of the Web for help.

  • Get workable solutions and helpful tips in a moment.

Just ask Solucija about an issue you face and immediately get a list of ready solutions, answers and tips from other Internet users. We always provide the most suitable and complete answer to your question at the top, along with a few good alternatives below.