• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
  • Mikalai Zaikin

LDAP and software applications

Ranch Hand
Posts: 137
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi guys,

I have a question more about design than code.

We want to use LDAP in our software but we have granular security - i.e. this person has access to these specific things. The specific things (such as administration of users, access to certain reports, etc) are specific to our software.

So, my questions are:

1. If a user exists in LDAP, how do you tell LDAP that they can log into the software? Do you usually start with an LDAP admin tool or get the software installer to update the LDAP record?

2. How are the specific security settings (for our application only) usually managed with LDAP? We don't want to write something that messes up the company LDAP with loads of software specific attributes - or is that how it's done? Do we create a sub-tree off the user for our application?

I guess what I'm saying is: I get the whole 'finding a user' thing with LDAP - can someone describe how it works in software that's a bit more complicated than 'Can they login or not?'.

Any help is much appreciated.

Don't get me started about those stupid light bulbs.
    Bookmark Topic Watch Topic
  • New Topic