Neither the property "username" exist in class "App\Entity\User". about hwioauthbundle

[stloyd]

This is not a bug IMO. There is a clear note in the docs you pointed:

Remember that you can (and you should) also overwrite templates provided by this bundle

Thus you should adjust the base templates from the bundle to your needs, we cannot ensure that the end user sets all things.

[sovetski]

@stloyd and what about

Also in src\Resources\config\routing\connect.php the registration route is hardcoded, we should be able to customize it.
In my case I am using Symfony's default Security solution to handle my users, and I already have a route named register, I don't want to get double route with registration, and If I am not wrong, with the current version it is not possible

[stloyd]

You can add your route, what is important is just the name and parameters in the route, we don't care about what path the route has.

[sovetski]

@stloyd I don't see anywhere on the documentation which says how to customize the route after user tries to login with a not existing account. It redirects automatically to the route /connect/registration which is hardcoded in src\Resources\config\routing\connect.php.

[stloyd]

You don't see this cause setting routes are basics of usage of Symfony.

As said you're not forced to use that routing, you can create a new routing file like this:

use HWI\Bundle\OAuthBundle\Controller\Connect\ConnectController;
use HWI\Bundle\OAuthBundle\Controller\Connect\RegisterController;
use Symfony\Component\Routing\Loader\Configurator\RoutingConfigurator;

return static function (RoutingConfigurator $routes) {
    $routes->add('hwi_oauth_connect_service', '/service/{service}')
        ->controller([ConnectController::class, 'connectServiceAction'])
        ->methods(['GET', 'POST']);

    $routes->add('hwi_oauth_connect_registration', '/my-own-registration/{key}')
        ->controller([RegisterController::class, 'registrationAction'])
        ->methods(['GET', 'POST']);
};