-
-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Recently joined Members missing in Network-Members API #539
Comments
Thx, will add a fix.
No, such endpoint does not exist. |
Hi sinamics, thanks, this would be great improvement for our use case! 😊 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🐛 Describe the Bug
If new Members join to a ZT network they are missing in in the Network-Members API for up to 5 Minutes. There seems to be a cache or something that delays everything. If you open the corresponding network in the Web UI this seems to update the cache.
This affects API Endpoints like:
🔍 Steps to Reproduce
Join a new Client to a Network (where the client was not authenticated yet) and call the
POST /network/:networkId/member/:memberId
API to authenticate the new member about 10 seconds later. The API responds that the member is not found. It would now take up to 5 minutes, but if you open the corresponding network in the Web UI once, the member is instantly found by the API afterwards🌐 Browser
Chrome
🔧 Deployment Type
✨ Expected Behavior
New members should be instantly available to the API or there should be a simple API Call to "refresh" the network members as the Web UI seems to do it. Or is there already such an undocumented endpoint?
📋 ZTNET Logs
No response
🖼 Screenshots
No response
The text was updated successfully, but these errors were encountered: