Well, I’ve overrided Login core plugin writing a custom authentication by following HttpAuthLogin plugin example.
Now I’ve discovered console core:archive command and misc/cron/archive.php script are failing because of an error:
INFO CoreConsole[2014-04-16 11:05:26] [582c7] ERROR: Got invalid response from API request: http://127.0.0.1/piwik/index.php?module=API&method=API.get&idSite=1&period=day&date=last2&format=php&token_auth=7917f2596f8bb70c954893f200ba6274&trigger=archivephp. Response was 'a:2:{s:6:"result";s:5:"error";s:7:"message";s:126:"Non puoi accedere alla risorsa richiesta perché è necessario essere autorizzati per l'accesso 'view' per il sito con id = 1.";}'
In the Login plugin’s description cell (in plugins page) i can read: “Login Authentication plugin, reading the credentials from the config/config.ini.php file for the initial Super User, and from the Database for the other users. Can be easily replaced to introduce a new Authentication mechanism (OpenID, htaccess, custom Auth, etc.).”
Well, looks like my new authentication plugin can’t read superuser credentials from the config.ini.php and looks for first superuser into db but when it’s found, this user have any ‘view’ right on sites profiles because he’s superuser status.
Did you tested crontabbing using HttpAuthLogin? How can I run crontab using first installed superuser instead of DB superusers?