Having a similar error. I get error code 10124 when I generate my jwt from jwt.io.
Here is my header, payload, and verify signature:
{
“alg”: “HS256”,
“typ”: “JWT”
}
the appKey I fill with my SDK key from my SDK credentials on the zoom marketplace. The SDK Secret I have pasted in with and without quotes. iat < tokenExp < exp. I have my domain still set to https://zoom.us
just give the dreaded 10124 return. Authenticating using my app key and secret works fine. I have tried setting “tokenExp” to values before, equal to and after “exp”, to no effect.
JWT.IO reports the “iat” and “exp” values as correct dates.
I’m really struggling to make this work. Failing at the first hurdle in the sample app makes it very difficult to work with this SDK.
Is this the same version (v_2) that your site points to? The readme in v_2 that your site points to refers to the latest project as ‘~new’ instead of ‘~v_2’. The reason I ask is that I am dealing with the same errors this conversation thread addresses, using the v_2 from your site.
Could you provide a URL here for each, please … (for my sanity)
URL of zoom-sdk-windows-master latest
URL of zoom-c-sharp-wrapper-master latest
Is v_2 the same as ‘new’? I have gotten errors with v_2 referencing ~DOT_NET_~WRAPPER vs ~C_SHARP~_WRAPPER so I cant be sure if I’m using a correct build.
OK I have built both projects, here’s what my issue was in case anyone hits the situation where no matter how they follow the instructions, and include everything in every conceiveable path, it can still not find linked symbols, and what the issue was. Hint C++/C# newbie pilot error.
When I first tried to build the combined solution, and chose (don’t do this) upgrade the tools reference, it caused an update force on windows 10. Then an install of VS 2015, then 17 etc. to handle incremental tools issues,and during all this some reference to Windows dlls version conflict (I’m assuming) caused the underlying issue. Reistallation of VS 2019 and a clean setup on the _V2 project enabled building both the C++ sdk project and the combined demo solution.
I just found the one-way upgrade issue warning in the SDK instructions; might be helpful to add this to the C# wrapper instructions if it saves other time/support tickets.
Thanks for the post and pardon the late response. Please try to make the “exp” larger than the “tokenExp”. Everything else looks good. Please have a try.
Thanks for the posts and pardon the late response. Glad to hear that you have found the solution. I will forward your feedback to the doc team to enhance the instructions. Let me know if any other questions.
I am having the exact same problem as everyone. I entered all the required sections carefully, but yet I keep getting the 10124 return on the sample app. What can I do to make it work? here’s what i entered into the JWT.io: [version v5.2.41727.0928]
{
“alg”: “HS256”,
“typ”: “JWT”
}
Epoxy flake flooring Brisbane prepared by epoxy flooring redheads and they provide good service for home s and offices.
Benefits Of Ultra Flake:
Epoxy Ultra Flake is an amazing waterproof flooring system, great for both residential and commercial use. Interior and exterior areas like basements, workshops, garages, patios, driveways, changing rooms and showers can benefit from epoxy flake flooring.