Omada Controller v5 - External Portal Stopped Working After Updating From v4 to v5

Omada Controller v5 - External Portal Stopped Working After Updating From v4 to v5
Omada Controller v5 - External Portal Stopped Working After Updating From v4 to v5
2022-03-10 08:57:16 - last edited a week ago

This Article Applies to:

Omada Controller v5

 

Issue Description/Phenomenon:

Recently we received feedback that the external hotspot setup stopped working after updating Controller from v4 to v5, and the error message is related to the API info, like the example below

..."status":404,"error":"Not Found","message":"","path":"/api/v2/hotspot/login"}.

 

Available Solutions:

Omada Controller v5 has adjusted API for External Portal, please refer to the following FAQ to modify the External Portal setup. The Requirements of Establishing an External Portal Server (above Omada SDN Controller 5.0.15)

 

Kind Note: 

Compared to Omada Controller v4, the main changes on Controller v5 are as follows:

1. Add Controller ID to the URL for hotspot login and client information submission.

2. Add the HTTP header, which carries the CSRF Token.

 

Feedback:
 

If this was helpful, welcome to give us Kudos by clicking the thumbs-up button below.

If there is anything unclear in this solution post, please feel free to leave your comment.

 

Thank you in advance for your valued feedback!

New to the TP-Link Community? Getting Started from this thread: https://community.tp-link.com/en/business/forum/topic/551684
0
0
#1
Options