Secret keys list was hard-coded when decoding authentication token about livesdk-for-windows HOT 5 CLOSED

I am experiencing the same issue even with SDK 5.3.
I've not found a way to work around it unless I modify the code to skip that verification, which I wanted to avoid for security reasons and to avoid having to maintain a clone of the SDK's source.
@euyuil Did you find some other workaround? I even tried creating a new app in Live, so that this KeyId would reset to 0, but it seems to be always starting at 1.

from livesdk-for-windows.

@jdom I solved the problem the same way as yours. But I don't think it's a good way, either.

from livesdk-for-windows.

Thanks for reporting this issue. It looks to me that the kid (KeyId) value can be ignored. I will reach out to server team before making a fix on this.

Thanks,
Lin

from livesdk-for-windows.

I got some response from server team. The KeyId value is designed to be used when roll over a new app secret. We will be applying a fix on this code.
At the moment, to unblock you, you can edit the code here and replace the 0 with the right index value you got from the App Settings page (v#: in your case, it is 1).

Thanks,
Lin

from livesdk-for-windows.

Issue still exists in version 5.6

from livesdk-for-windows.