silex

I have a class UserMapper <?php namespace Models; use Symfony\Component\Security\Core\User\UserProviderInterface; use Symfony\Component\Security\Core\User\UserInterface; use Symfony\Component\Security\Core\Exception\UnsupportedUserException; use Symfony\Component\Security\Core\Exception\UsernameNotFoundException; use \PDO; class UserMapper implements UserProviderInterface { /** * Database connection. */ var $db = NULL; /** * Constructor function. Loads model from database if the id is known. * * @param $db * Database connection */ function __construct() { $this->db = ConnectionProvider:

I've been working on making an api that accepts api keys and followed the instructions on http://symfony.com/doc/current/cookbook/security/api_key_authentication.html using a database table to hold the api keys. Is there a better way to handle this strictly using silex's firewall settings? Symfony does not come with an API key authenticator out of the box, but you can create one (not easily, especially for beginers) following the cookbook entry you've posted. So the short answer to your questions is that no, there is no better way if you want to use the security library. But, there is some on

The problem I'm building a small application with Silex . It's divided between a REST application and a website. ( two controllers , same app). The website has installed its own custom error handler , which returns a user friendly html page. The problem is that in the part dedicated REST application, I should somehow handle exceptions to return type [json] and content different from the error handler's custom website. With Symfony2 This argument can also be applied to Symfony2, I would like also possible solution for it! A first solution for Silex Wrap the methods in try-catch block in order

I'm having quiet weird problem with catching SwiftMailer's exceptions in Silex. I want to send an email like this: try { $message = \Swift_Message::newInstance() ->setSubject('subject') ->setFrom(array('form')) ->setTo(array('to')) ->setBody('body'); $app['mailer']->send($message); } catch (\Swift_TransportException $e) { $app['logger']->addError('Unable to send welcome email'); } I know it's not going to send any email on localhost and I'm expecting it to fail but why I can't catch the Swift_TransportException exception in try - catch block? It just prints: Fatal error: Uncaught exception

Context : I created a custom user provider for my Silex Application and I can now register and log my own user perfectly. However, I need now to automatically log in my user after registration and this doesn't work. Here is my security section : 'secured' => array( 'pattern' => '^/', 'anonymous' => false, 'form' => array('login_path' => '/login', 'check_path' => '/login_check'), 'logout' => array('logout_path' => '/logout', 'invalidate_session' => true), 'users' => $app->share(function () use ($app) { return new Partner\DAO\PartnerDAO($app['db']); }) ) Here is my userProviderInterface : public

I am developing a project with silex-skeleton in its most recent version. When trying to use the share method shows me the following error: Code: $app['login'] = $app->share(function() use($app) { return new Model\UserModel($app); }); Error: Attempted to call method "share" on class "Silex\Application" Any suggestions or possible cause of this failure mTorres Silex 2.0 is using Pimple 3.0 which has removed the shared method, now all services are shared by default, if you want a new instance you must call the factory method as stated in the changelog for version 2.0 . So if you want a login