Authorizing Client via API

Authorizing Client via API

Authorizing Client via API
Authorizing Client via API
2025-02-24 14:11:38 - last edited 2025-02-25 09:15:45
Hardware Version: V5
Firmware Version: 5

Hi!


I have successfully authorize a client via script on my external portal. But for the life of me I can't figure how to specify time duration, e.g. authorize a client for 60minutes. It always defaulted to 8hrs. When making a portal, I can see there is a default Authentication Timeout of 8hrs on "No authentication" option, but not available on "External Portal" option.

From the documentation I see this: /openapi/v1/{omadacId}/sites/{siteId}/hotspot/clients/{clientMac}/auth

Is it possible to send an API request authorizing a client with time duration?

Thanks!

  0      
  0      
#1
Options
1 Accepted Solution
Re:Authorizing Client via API-Solution
2025-02-25 07:14:12 - last edited 2025-02-25 09:15:45

Hi  @drawpaint 

 

Can you find something like custom?

 

Recommended Solution
  0  
  0  
#2
Options
4 Reply
Re:Authorizing Client via API-Solution
2025-02-25 07:14:12 - last edited 2025-02-25 09:15:45

Hi  @drawpaint 

 

Can you find something like custom?

 

Recommended Solution
  0  
  0  
#2
Options
Re:Authorizing Client via API
2025-03-02 14:25:36

  @Vincent-TP Hi, I don't see this option as available in Authentication Type:  External Portal Server. The screen shot you showed is only for voucher. My external portal will handle credits, and based on that it will send an auth to the controller and preferrably with the specified time duration.

  0  
  0  
#3
Options
Re:Authorizing Client via API
2025-03-03 06:27:43

  @drawpaint 

This is determined by the external portal server.

You may contact the server support for help.

  0  
  0  
#4
Options
Re:Authorizing Client via API
3 weeks ago

  @Vincent-TP I made the external portal server, it is where clients pay and add time credits to their account. What's next is this external server to send an authentication via api to the omada controller to authorize the client with a time duration. Do you get what I mean? There is already an auth request in the API which I am already successful, but it defaults to 8hrs. This is easily done in the UNIFI controller.

Please refer to the flow below:
1. Guest connect to WiFi and is redirected to my external Portal.
2. Guest pay and add credit to his account. e.g. has 10hrs credit.
3. External Portal server then sends an authorization to the Omada controller via API request authorizing the guest for 10hours.

  0  
  0  
#5
Options