6.45.8 - authentication failure
ivan5rov opened this issue · 2 comments
I started having a problem using the API since one of my routers was upgraded to 6.45.8 (current long term release). It keeps giving me login failed errors despite i am 100% certain password is correct.
I found this thread which might be related: https://forum.mikrotik.com/viewtopic.php?t=136475, though I can't believe nobody noticed/fixed this for almost an year (the date of last posting in that MT thread)
edit: Based on issue #53 I noticed the dev branch uses the new auth and it indeed works. Are there plans to integrate new authentication in some way (for example - select type (legacy/new) in connection to go around this auth discontinuation from RouterOS end?
The auth in dev-develop is made to try the new protocol first, and fallback to the legacy one on failure, so it works on all RouterOS versions.
I'm having a bit of a difficulty in making a PHAR release, which is why there also isn't a tagged version. Combined with the de facto death of pear2.php.net, this means that if I just tag the dev-develop as a version and no phar, only composer users can use it... And they can use it now anyway, without such a release, so I've decided I'll only do a tag release once I can make a PHAR.
As for explicitly selecting an authentication type, yes, I have some ideas, but I'll only be doing them after a tagged release.
Thanks @boenrobot! I am therefore closing this report as I feel it can be considered solved.