This bundle is in development
This bundle sets up the NTLM authentication provider for your application. If there is NTLM data provided by the browser, then the application will try and authenticate the provided username against your user provider/chain user providers
- Symfony 2.0.x
-
Register the namespace
BrowserCreative
to your project's autoloader bootstrap script:// app/autoload.php $loader->registerNamespaces(array( // ... 'BrowserCreative' => __DIR__.'/../vendor/bundles', // ... ));
-
Add this bundle to your application's kernel:
// app/AppKernel.php public function registerBundles() { return array( // ... new BrowserCreative\NtlmBundle\BrowserCreativeNtlmBundle(), // ... ); }
-
Update your security.yml:
security: factories: - "%kernel.root_dir%/../vendor/bundles/BrowserCreative/NtlmBundle/Resources/config/security_factories.xml" providers: ... firewalls: secured_area: pattern: ^/ ntlm_protocol: provider: chain_provider redirect_to_login_form_on_failure: true ntlm_form_login: provider: chain_provider remember_me_parameter: _remember_me logout: ~ anonymous: true ...
- The two authentication providers (NtlmProtocolAuthenticationProvider, NtlmFormLoginAuthenticationProvider) pass tokens to the user provider instead of the username. Feel free to change this back, it's just that our User Providers require the tokens because they rely on the password to access the database (LDAP)