So I’ve been trying to find a way to login a user from the Mikrotik API and I understand there’s no implementation but I don’t understand why there is no implementation as it doesn’t seem impossible from a design point of view. i.e. I can login a regular user via API, but not a hotspot user. Also the hotspot login which happens first on the client sides, still posts some information to the router and I guess saves some sort of information in the browser SESSION, so this should be certainly possible to have on the API and it would be possible to make a separate library for it.
What I don’t understand is why such a common feature doesn’t exist on the API. I could be not making any sense here or missing some important information but I’d like to be educated.
Thanks
Please describe in details what exactly yo want to do. Users log in to the router via API to send API commands, I do not understand how it is related to hotspot user logins.
My argument is that the Mikrotik Hotspot is part of the Router/RouterOS and supports user Hotspot login via web, but there is no API for this. I can for example create hotspot users or even manage Hotspot users from API but I can’t perform a hotspot user authentication whereas it is technically possible and also a common function.
A typical example can be authenticating hotspot users automatically via API for example. Let’s say you have a button and a custom login form (different from mikrotik) and you wanted them to login via your own system. You could want a way to log them in normally and then log them in automatically via API internally.
thats already done by several companies for internal use.
API and hotspot kinda mutually irrelevant topics, unless you want to implement “alternative hotspot” via API or anything else(billing, monitoring, etc), which is also quite popular thing to write over API.