MAC Caching consists of two parts:
- A WEBAUTH that handles the captive portal authentication and injects timestamps into the endpoint database.
- A MAC Authentication service and leverages the timestamps injected during captive portal authentication.
Best-practice is to have two separate services for these as MAC Auth in general is done in a separate service from user authentication services.
Does this answer the question, or did I miss the point?