From 7547e6eccaab729e5f7518cbcfc20c3d5adfcee4 Mon Sep 17 00:00:00 2001
From: Chris Hiszpanski <chris.hiszpanski@verkada.com>
Date: Wed, 9 Mar 2022 00:00:14 -0800
Subject: [PATCH] Fix ResourceEndpoint length check (#1411)

ResourceEndpoint length check mistakenly uses ChannelName max length.
---
 src/source/Signaling/LwsApiCalls.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/source/Signaling/LwsApiCalls.c b/src/source/Signaling/LwsApiCalls.c
index 2009bb31e0..1e898c394b 100644
--- a/src/source/Signaling/LwsApiCalls.c
+++ b/src/source/Signaling/LwsApiCalls.c
@@ -1083,7 +1083,7 @@ STATUS getChannelEndpointLws(PSignalingClient pSignalingClient, UINT64 time)
                     i++;
                 } else if (compareJsonString(pResponseStr, &tokens[i], JSMN_STRING, (PCHAR) "ResourceEndpoint")) {
                     strLen = (UINT32) (tokens[i + 1].end - tokens[i + 1].start);
-                    CHK(strLen <= MAX_CHANNEL_NAME_LEN, STATUS_INVALID_API_CALL_RETURN_JSON);
+                    CHK(strLen <= MAX_SIGNALING_ENDPOINT_URI_LEN, STATUS_INVALID_API_CALL_RETURN_JSON);
                     pEndpoint = pResponseStr + tokens[i + 1].start;
                     endpointLen = strLen;
                     endpoint = TRUE;