The file is editable.
You can add anything you want.
I do not know more, I’m not following HotSpot,
for me is a dead market.
Any time spent on this do not have any proper revenue.
2,4GHz spectrum are dead and LTE/5G technologies on every device, make HotSpot useless.
Hello, https://help.mikrotik.com/docs/pages/viewpage.action?pageId=56459266 According article it works automaticaly: This DHCP option field is enabled automatically, but only if the router has a DNS name configured and has a valid SSL certificate (so that the login page can be accessed over HTTPS). When these requirements are met, a special DHCP option will be sent, containing a link to https:///api. This link contains information in JSON format, instructing the client device of the captive portal status, and the location of the login page.
I’ve not made CCR1009 do it. I setuped certificate and DNS name, but https://dnsname/api responds “404 not found”. There’s not editable api.json. Has anybody done it?
We have configured option 114 successfully.
Now on the Android 11 smartphone the captive portal is triggered and we can log in and we can navigate.
In any case, after authentication, the wifi network does not recognize successful authentication and prompts us to log in with the wifi symbol with an exclamation / question mark.
What can be done to communicate the successfullly connection to the device?
the problem is that even if “venue-info-url” can be updated on api.json the corresponding Captive Portal API “NOTIFICATION” is NEVER TRIGGERED by mikoritk HotSpot.
in other words Mikrotik do not comply with the CAPTIVE PORTAL SPECIFICATION, and do not NOTIFY the Captive Portal (Notify mean OS NOTIFICATION with INTENT → to venue-info-url)
when user connet to Captive Portal, the EVENT shold be triggered and the corresponding NOTIFICATION MUST APPEAR and link to “venue-info-url” as reported on this site (look at the image) https://globalreachtech.com/ietf-capport-api-globalreachtech/
Mikrotik simply does not show the notification, this is USELESS
Google, FB and all the other are going to REMOVE LOGIN FROM INTERNAL WEBVIEW.
If this “notification” will not be “focused” nobody will ever be able to login using OAuth2 in a few months