@pbk wrote:
Hi there,
it's nice to get updates and it's nice to get new features – but it's not nice to break things and don't tell anybody about it. Reading the release note for version 3.0.0 (https://developer.piwik.org/changelog#piwik-300) reveals no information that you've totally broken getUsers.
This method is no longer returning the users token. There's UsersManager.getTokenAuth but you can't use this because the API is not returning any useful information about the users password anymore (or getTokenAuth is broken, too because it's not accepting the passwords returned by the API), so this method is nonsense if the user did not enter his password. You're storing the password as an encrypted hash – fine, but you've broken it.
As far as I can tell, there's no way to retrieve the user data and the token using the API anymore – even for a superuser who should have access to everything when using the API. We may have different definitions of Superusers…
The only solution is to ditch this whole API stuff and access the database directly to request the token. But why exactly is there an API if users are forced to use the database instead?
I really hope for an update to fix this – until then I'll retrieve the stuff I need from the database, as we did in the 80ies without APIs.
And did I mention that "logme" isn't working, too? Because there's no useable password retrieved. And why isn't it possible to login using the token?
The FAQ says "If you want to provide a one-click automatic login to Piwik for your users, you can use the ‘logme’ mechanism […] To generate the md5 password, you need the user’s raw password and then call the md5() hash function on this raw password using your favorite programming language."
Where are these stored in the Database? Nowhere? Bummer!
Posts: 3
Participants: 2