Sponsored Content
Full Discussion: DSEE 6.3.1 with TLS:simple
Operating Systems Solaris DSEE 6.3.1 with TLS:simple Post 302423168 by jlliagre on Thursday 20th of May 2010 09:41:12 AM
Old 05-20-2010
ldap must be running on the standard port when running over ssl, ie 636. Running it on 1389 isn't supported with Solaris 10 and older.

This is fixed with OpenSolaris.

Bug ID: 4942874 RFE: native ldap client with ssl restricted to ports 636/389
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

How ldap authentiation works with TLS?

I am confused in understanding, how ldap authentication works. Anyone has any idea ? I also want to know when you create certificate where does openldap stores certificate information. $nilesh (1 Reply)
Discussion started by: ynilesh
1 Replies

2. Emergency UNIX and Linux Support

DSEE LDAP corruption

Today when someone was using Sun Identity Manager to modify a directory managed by Sun Directory Server Enterprise Edition (DSEE 6.3) IDM spit out an object class violation error (I verified that the input data was valid). It also corrupted the directory to the point where I can't even get dsadm to... (7 Replies)
Discussion started by: ilikecows
7 Replies

3. UNIX for Dummies Questions & Answers

TLS/SSL Openldap Centos 5.5

hi guys I configured my openldap but now I want to implement SSL-TLS This is my basic slapd.conf configuration include /etc/openldap/schema/core.schema include /etc/openldap/schema/cosine.schema include /etc/openldap/schema/inetorgperson.schema include ... (2 Replies)
Discussion started by: karlochacon
2 Replies

4. UNIX for Advanced & Expert Users

ldap over tls -- ssl cert help

Hey Guys, I am trying to setup ldap over tls in our lab. I am generating a self signed cert on the ldap server and importing that into the ldap system so it will use ldap over port 636. The clients will be a mix of solaris and redhat. I am lost on what I need to do on the client side to get... (0 Replies)
Discussion started by: s ladd
0 Replies

5. Cybersecurity

How to disable TLS 1.0 support in Solaris

Hey Guys, I have a couple servers that are getting flagged by by our network security team. How do I disable TLS 1.0 protocol within Solaris? The vulnerability is : CVE-2011-3389 TLS-SSL Server Blockwise Chosen-Boundary Browser Weakness (2 Replies)
Discussion started by: s ladd
2 Replies

6. UNIX for Advanced & Expert Users

SSL/TLS with openldap

Hello to all, I'm beguinner in Linux instalations and I'm trying to Communicate from Web Sites that i have running under apache with openLDAP for users authentication using SSL mediation that seems to be connected with LDAPS. Can someone advise me how to do this, I have already installed... (1 Reply)
Discussion started by: CPMarco
1 Replies

7. UNIX for Advanced & Expert Users

FTP over implicit TLS

Here are the essentials: un: myuser pw: mypasswd site: sftp.somesite.com port: 990 type: FTPS enc: FTP over implicit TLS program used: Curl 7.1.x on Hpux 11.31 I would like to "put" 1 file on there server. Here is my syntax, what am I doing wrong? curl -3 -v --cacert... (4 Replies)
Discussion started by: olyanderson
4 Replies

8. HP-UX

Sendmail TLS and Certificate?

We are running HP-UX 11v1 and are about to upgrade sendmail to 8.13.3 to allow support for TLS. Enabling TLS seems pretty straightforward, but I'm wondering if an SSL certificate is required for this. Our MS Exchange server does use a certificate. Do I need to arrange for a public certificate to... (3 Replies)
Discussion started by: jduehmig
3 Replies

9. AIX

AIX sendmail and tls

The situation Version AIX7.1/8.14.4 Compiled with: DNSMAP LDAPMAP LDAP_REFERRALS LOG MAP_REGEX MATCHGECOS MILTER MIME7TO8 MIME8TO7 NAMED_BIND NDBM NETINET NETINET6 NETUNIX NEWDB NIS NISPLUS PIPELINING SCANF STARTTLS USERDB USE_LDAP_INIT XDEBUG... (2 Replies)
Discussion started by: Linusolaradm1
2 Replies

10. Solaris

How to configure CUPS on Solaris 11.3 - TLS and no TLS?

We are implementing CUPS on a new Solaris 11.3 system. The same system will run an application where users can print to networked printers inside our organisation, or to a printer outside of our organisation over the internet. For users printing to internal network printers, no encryption is... (0 Replies)
Discussion started by: SallyB
0 Replies
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)
All times are GMT -4. The time now is 01:17 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy