10-05-2011
We are not using AD as LDAP server but I remember connecting to AD being described in this Redbook too:
IBM Redbooks | Integrating AIX into Heterogeneous LDAP Environments
The way how to configure your LDAP clients this way didn't change much from AIX 5 to AIX 7. Just some of the filesets you need have changed. In AIX 7 you need some of the Tivoli LDAP client packages instead but they are on the basic OS media.
If your basic LDAP connection with the secldapclntd (Secure LDAP Client Demon) is working, outsourcing RBAC security tables onto your LDAP server should be somewhat the similar when doing this to an AD or any other LDAP server.
This is described here:
http://www.redbooks.ibm.com/redpiece...7430.html?Open
9 More Discussions You Might Find Interesting
1. Windows & DOS: Issues & Discussions
Hi
Does anybody know the steps and requirements of the installation process of Windows Active Directory using Unix/Linux Bind DNS.
I will appreciate if somebody gives the answer. (1 Reply)
Discussion started by: Darwin Rodrigue
1 Replies
2. UNIX for Dummies Questions & Answers
Hello - I have a very vague question, which will probably result in vague answers because I don't have a lot of detailed information and I don't know a whole lot about active directory.
Our Windows/NT admin has been rolling out Active Directory over the past several weeks and as time goes on,... (1 Reply)
Discussion started by: rm -r *
1 Replies
3. UNIX for Dummies Questions & Answers
i would like to ask about unix with active directory..actually my situation is at ny place there already have dns server in unix based,i want to implement an active directory to the network..from what i read about active directory we have to used bind dns...some say that bind could not handle in... (1 Reply)
Discussion started by: nour
1 Replies
4. HP-UX
Hey,
I've asked questions about this project here before and gotten lots of help so I figured I'd give it another try.
I've recently set up my HP-UX environment to authenticate to a Windows Active Directory server (Windows Server 2003 R2).
I setup an account on Active Directory which works... (2 Replies)
Discussion started by: Rike255
2 Replies
5. IP Networking
Hello,
I am trying to authenticate through PEAP/mschap with freeradius 2.x and Active Directory.
I have followed this guide: Deploying RADIUS: Configuring Authentication with Active Directory
wbinfo works:
# wbinfo -a LOGIN%PASSWORD
plaintext password authentication failed
Could not... (0 Replies)
Discussion started by: sncr24
0 Replies
6. Red Hat
Hi Friends,
I need your help to get some solution of one of my problem.
Ours is a mixed domain. Most of the servers are windows and very little linux servers. We are using the MS AD for authentication. My problem is, I want to authenticate linux servers against AD. I donot want to use any... (1 Reply)
Discussion started by: arumon
1 Replies
7. Solaris
At the moment we are integrating LDAP in our environment.
Compared to Windows this process is much complicated and time consuming.
With Windows you had Active Directory and if you create a new server, you just add it to the domain and your finished.
Yes, I know Unix is not Windows.
Are there... (1 Reply)
Discussion started by: misterx12345
1 Replies
8. UNIX for Advanced & Expert Users
Is there anyone who is utilizing Active Directory (2008R2) for AIX user account management? If yes or if AD is possible with AIX systems, can you please share what to be done to get there?
Please advise. (1 Reply)
Discussion started by: Daniel Gate
1 Replies
9. UNIX for Beginners Questions & Answers
Hi,
How can we check users added through LDAP or AD. Users added through a group of AD or LDAP group. (2 Replies)
Discussion started by: Nishit
2 Replies
LEARN ABOUT REDHAT
ldap_free_urldesc
LDAP_URL(3) Library Functions Manual LDAP_URL(3)
NAME
ldap_is_ldap_url, ldap_url_parse, ldap_free_urldesc, ldap_url_search, ldap_url_search_s, ldap_url_search_st - LDAP Uniform Resource Locator
routines
SYNOPSIS
#include <ldap.h>
int ldap_is_ldap_url( url )
char *url;
int ldap_url_parse( url, ludpp )
char *url;
LDAPURLDesc **ludpp;
typedef struct ldap_url_desc {
char * lud_scheme; /* URI scheme */
char lud_host; /* LDAP host to contact */
int lud_port; /* port on host */
char * lud_dn; /* base for search */
char ** lud_attrs; /* list of attributes */
int lud_scope; /* a LDAP_SCOPE_... value */
char * lud_filter; /* LDAP search filter */
char ** lud_exts; /* LDAP extensions */
/* may contain additional fields for internal use */
} LDAPURLDesc;
ldap_free_urldesc( ludp )
LDAPURLDesc *ludp;
int ldap_url_search( ld, url, attrsonly )
LDAP *ld;
char *url;
int attrsonly;
int ldap_url_search_s( ld, url, attrsonly, res )
LDAP *ld;
char *url;
int attrsonly;
LDAPMessage **res;
int ldap_url_search_st( ld, url, attrsonly, timeout, res )
LDAP *ld;
char *url;
int attrsonly;
struct timeval *timeout;
LDAPMessage **res;
DESCRIPTION
These routines support the use of LDAP URLs (Uniform Resource Locators) as detailed in RFC 2255. LDAP URLs look like this:
ldap://hostport/dn[?attrs[?scope[?filter[?exts]]]]
where:
hostport is a host name with an optional ":portnumber"
dn is the search base
attrs is a comma separated list of attributes to request
scope is one of these three strings:
base one sub (default=base)
filter is filter
exts are recognized set of LDAP and/or API extensions.
Example:
ldap://ldap.example.net/dc=example,dc=net?cn,sn?sub?(cn=*)
URLs that are wrapped in angle-brackets and/or preceded by "URL:" are also tolerated. Alternative schemes such as ldaps:// and ldapi://
may be parsed using the below routines as well.
ldap_is_ldap_url() returns a non-zero value if url looks like an LDAP URL (as opposed to some other kind of URL). It can be used as a
quick check for an LDAP URL; the ldap_url_parse() routine should be used if a more thorough check is needed.
ldap_url_parse() breaks down an LDAP URL passed in url into its component pieces. If successful, zero is returned, an LDAP URL description
is allocated, filled in, and ludpp is set to point to it. If an error occurs, a non-zero URL error code is returned.
ldap_free_urldesc() should be called to free an LDAP URL description that was obtained from a call to ldap_url_parse().
ldap_url_search() initiates an asynchronous LDAP search based on the contents of the url string. This routine acts just like
ldap_search(3) except that many search parameters are pulled out of the URL.
ldap_url_search_s() performs a synchronous LDAP search based on the contents of the url string. This routine acts just like
ldap_search_s(3) except that many search parameters are pulled out of the URL.
ldap_url_search_st() performs a synchronous LDAP URL search with a specified timeout. This routine acts just like ldap_search_st(3) except
that many search parameters are pulled out of the URL.
SEE ALSO
ldap(3), ldap_search(3)
The LDAP URL Format, RFC 2255, Tim Howes and Mark Smith, December 1997.
ACKNOWLEDGEMENTS
OpenLDAP is developed and maintained by The OpenLDAP Project (http://www.openldap.org/). OpenLDAP is derived from University of Michigan
LDAP 3.3 Release.
OpenLDAP 2.0.27-Release 17 October 2000 LDAP_URL(3)