cisco-systems/directory-bundle

Cisco Global VE directory bundle

Installs: 16

Dependents: 0

Suggesters: 0

Security: 0

Stars: 1

Watchers: 5

Forks: 0

Open Issues: 0

Type:symfony-bundle

3.0 2016-08-16 13:51 UTC

This package is not auto-updated.

Last update: 2024-04-13 17:07:58 UTC


README

Symfony bundle for accessing Active Directory servers.

Installation

Add the bundle to the requirements in your composer.json file:

"cisco-systems/directory-bundle": "dev-master"

Register the bundle in your AppKernel:

public function registerBundles()
{
    $bundles = array(
        // ...
        new CiscoSystems\DirectoryBundle\CiscoSystemsDirectoryBundle(),
        // ...
    );
    // ...
    return $bundles;
}

Configuration

Add configuration for the bundle to your config.yml file. You can configure as many directories as you like. A minimal bundle configuration would look like the following:

cisco_systems_directory:
    default_directory: main
    directories:
        main:
            servers:
                primary:
                    host: ads1.example.com

A more extensive configuration might look like this:

cisco_systems_directory:
    default_directory: main
    directories:
        main:
            repository: 'MyProject\\MyBundle\\Directory\\MyDirectoryRepository'
            default_rdn: '%myAppsLdapUsername%'
            default_password: '%myAppsLdapPassword%'
            servers:
                primary:
                    host: ads1.example.com
                secondary:
                    host: ads2.example.com

It's generally advisable to put usernames and passwords into your parameters.yml file and reference those parameters as shown.

Note the repository key in the configuration example above: this can be used to create custom query repositories in your application level bundles, containing methods tailored to your directory and your application.

If left unconfigured, the default repository provided by this bundle offers a simple search() method that should cover most needs. The default repository class is CiscoSystems\DirectoryBundle\Directory\QueryRepository.

Usage

In your controller you then simply request the query repository for your directory from the service provided by this bundle and call a repository method on it. If you do not provide a parameter for getRepository() it will use the configured default directory.

// Example using the configured default directory and the default query repository with the configured Base Distinguished Name for that directory:
$repository = $this->get( 'cisco.ldap' )->getRepository();
$result = $repository->search( $filter );

// Example using the configured default directory and the default query repository, specifying the Base Distinguished Name:
$repository = $this->get( 'cisco.ldap' )->getRepository();
$result = $repository->search( $filter, $baseDn );

// Example using a specific directory and a custom query repository:
$repository = $this->get( 'cisco.ldap' )->getRepository( 'main' );
$result = $repository->myCustomRepositoryMethod( $parameter, $anotherParameter );

Custom query repositories

If you need more than the basic search() method provided by the default repository, you can define your own query repositories in your application-level bundles. Simply extend the default repository and use the repository key as shown in the configuration example above to let the cisco.ldap service know what class it needs to instantiate.

When writing your custom repository methods, and you need to do something that the search() method of the default repository class cannot cover, use the default repository's $link property for PHP's ldap_* functions.

Performing an LDAP bind with a specific RDN and password

If you do not configure a default RDN and password, or if you want to use different ones in your code somewhere, you can do that in two ways.

  1. Specify the configured directory name when calling getRepository(), and add the RDN and password as further parameters:

    $repository = $this->get( 'cisco.ldap' )->getRepository( 'main', $bindRdn, $bindPassword );

  2. Or, if you want to re-bind your application to an already connected directory, use the repository's bind() method for binding to a specific RDN and password combination:

    $repository->bind( $bindRdn, $bindPassword );

That's all.

If you do not want to configure a default RDN and password but still don't want to specify the RDN and password every time you have to perform a bind because it will always the username and password of the currently logged on user, you can set the bind_authenticated_user variable for that directory in your bundle configuration to true.

Even if you do that you can still perform an anonymous bind by using the fourth parameter of the getRepository() method and set it to false:

$repository = $this->get( 'cisco.ldap' )->getRepository( 'main', '', '', false );

Authentication

You can also use this bundle to authenticate your users against a directory. For this purpose the bundle provides a simple form authenticator service. To use this service implement a simple_form login as described in the Symfony Cookbook article on custom authenticators.

Note that in this case you do not need to specify an encoder in your security.yml file, as the password validation is handled by the directory you're authenticating against.

An example security configuration might look like this:

security:
    providers:
        ldap:
            id: cisco.ldap.userprovider
    firewalls:
        main:
            pattern: ^/
            anonymous:  true
            simple_form:
                authenticator: cisco.ldap.authenticator
                check_path:    CiscoSystemsDirectoryBundle_logincheck
                login_path:    CiscoSystemsDirectoryBundle_login
            logout:
                invalidate_session: true

If you need to do more with your User objects than simply authenticating them, extend the user provider from this bundle and replace it in the above example.

Don't forget to import the routing for this bundle in your main routing.yml file:

ldap:
    resource: "@CiscoSystemsDirectoryBundle/Controller"
    type:     annotation

You will likely also want to override the login template.