Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m looking for the best way to provide authorization, authentication, and auditing to web services. I’ll be using a web service gateway appliance deployed to the DMZ, and there will be an LDAP instance as a user store behind the firewall. How should it be built?
Cheers
KA
Update As pointed out in an answer below, LDAP isn’t ideal for auditing. We’re now looking at a call to our CRM system for this function as we can audit the usage by customer.
Authentication is fairly standard. When trying to verify a username and password, first bind as a user with the privilege of seeing all users, and search for an entry with the provided username in the appropriate field (probably ‘uid’). Once you’ve found the entry, get its DN and try to bind as that entry using the supplied password.
Authorization is usually handled with either ‘dynamic groups’, where you have a multi-valued attribute in each user object that says what privileges the user has, or using ‘static groups’ where you have objects of a class resembling ‘groupOfNames’ and stick the DNs of all members into the ‘member’ attribute.
Do auditing however you like. LDAP is probably not the best way to save audit data. You could stick it in a database if you like, or just use syslog.