This is a variation on a question asked previously, but sufficiently different that the answer there (using a default realm) can’t be used as far as I can tell.
Scenario: I want to allow user on our hotspot to be able to use a ticket issued on an external radius system as an alternative login mechanism to our primary one. Our external freeradius server already understands and proxies the different realms set up for this correctly: Normal logins take place in the NULL realm as username (ie. without a domain), and tickets in the ‘ticket realm’ are proxied via the ticket.domain as ticketnr@ticket.domain.
All of this works fine as long as I can get ticket users to enter their ticket number as ticketnr@ticket.domain, however, as it happens the tickets themselves only have a ticketnr (without the domain), so I was wondering if I could set up a secondary login screen on the hotspot (ie. a link labelled: "Click here if you have a ticket:) and have them log in as ‘ticketnr’ and then either specify the realm in a hidden field or somehow otherwise appending “@ticket.domain” to the input upon submission. The latter could probably be done in javascript, but I don’t want any unnecessary dependencies so is the former possible? I’ve tried adding
<input type=hidden name="realm" value="@ticket.domain" />
to the form, but that does nothing.
Suggestions from more experienced Mikrotikers welcome!