Tag Info

Hot answers tagged

3

This is a normal behavior. UserAccountControl refers only to the user in the directory. Exchange add many attributes with which you can determine if a LDAP user has a mailbox. I'd say that msExchMailboxGuid would be the best, since every active mailbox must have one, and exchange delete the value when the mailbox is disabled (Tested on Exchange 2010 with ...


2

If you haven't consider sniffing the traffic between the LDAP server and the WebLogic server. I suspect you're going to see a failure similar to Google Chrome's failures of TLS 1.2 key exchange. You might try removing the new cipher suites that MS14-066 adds to see if that changes the behavior. Microsoft has updated the MS14-066 patch to remove these ...


1

After many tries I've found the solution. The problem was in incorrect VirtualHost configuration for git-http-backend. Here's my working config: <IfModule mod_ssl.c> <VirtualHost _default_:443> DocumentRoot /git/myrepos SetEnv GIT_PROJECT_ROOT /git/myrepos SetEnv GIT_HTTP_EXPORT_ALL ScriptAlias /myrepos/ ...


1

the GidNumber is unlimited. The GID number is defined as an integer in the schema definitions attributetype ( 1.3.6.1.1.1.1.1 NAME 'gidNumber' DESC 'An integer uniquely identifying a group in an administrative domain' EQUALITY integerMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 SINGLE-VALUE ) According to RFC 4517 LDAP: Syntaxes and ...


1

Items are "entries". The "path" to an item is its DN, or Distinguished Name. References: Relative article on Microsoft's MDSN Link from RHEL7 documentation


1

There are actually two disabled states for an Exchange mailbox. What many people consider "disabling" occurs when the Disable-Mailbox cmdlet is run. This actually removes most of the Exchange attributes from the account, and disconnects the mailbox. There is however an AD attribute msExchUserAccountControl. If this is set to 2, the mailbox is ...


1

OpenSSL can be a bit.. twitchy.. about what certificates it trusts - sometimes it won't use the system's trusted certificate store. Adjust its config in the openssl.cnf if you're so inclined to make it trust the right store. For ldapsearch, same kind of deal - you'll want to set the trusted certificate in ldap.conf to make it actually use the trusted ...


1

Effectively, there exist two approaches to use LDAP to authenticate. The first one tries to use the username and password you entered in the web browser to bind to the ldap server (this is LDAP speak meaning to login to the LDAP server). If the bind is successful, the username and password where correct and you are logged into your website. However, this ...


1

At first glance, in the manual, Kerberos with SPNEGO is supported out of the box: Similarly to Hadoop RPC, Hadoop HTTP web-consoles can be configured to require Kerberos authentication using HTTP SPNEGO protocol (supported by browsers like Firefox and Internet Explorer).


1

This is how we did it on our boxes, so be warned, it might not apply to your setup. A few caveats: Our server has a valid CA-signed certificate, be sure to modify ldap_tls_cacert if yours has a self-signed certificate (which is bad (tm) anyway). We use LDAP to provide sudo rules, to leave that out if you don't want it. You might want to set ...


1

Do i need a new bind to the server referred to? Yes. If so, is it neccessary, that the username and password i used for the root system will also work for the subsystem? No. Is there an easier way to tell an ldap search to chase referrals on its own? There are various OpenLDAP slave replication configuration options about that. Depending on ...


1

We have a Kerberos SSO in our Centos servers, so the problem was related to that. The kerberos ticket only lasts 12 hours and its generated every time we ssh to our servers. So the next day (after a 12 hours period) JBoss could not connect to a network shared folder (because of ticket expiration), does timeout with no error logs related to that. We already ...


1

You need to have all of the following for LDAPS to work: Configure the client to trust the CA that issued the certificate (or if using a hierarchical PKI, the root CA) Configure the client to access the Domain Controller server via FQDN The FQDN of the Domain Controller server must resolve correctly in DNS The FQDN of the Domain Controller server ...



Only top voted, non community-wiki answers of a minimum length are eligible