You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 27, 2018. It is now read-only.
Is there a reason why SHA256 is not registered as an accepted signature method?
When I'm trying to authenticate a LTI launch request signed with SHA256 I'm getting an error from \IMSGlobal\LTI\OAuth\OAuthServer::get_signature_method that only SHA1 can be used.
Hey,
Is there a reason why SHA256 is not registered as an accepted signature method?
When I'm trying to authenticate a LTI launch request signed with SHA256 I'm getting an error from
\IMSGlobal\LTI\OAuth\OAuthServer::get_signature_method
that only SHA1 can be used.If we add this line to https://github.com/IMSGlobal/LTI-Tool-Provider-Library-PHP/blob/master/src/ToolProvider/ToolProvider.php#L772 everything works as expected:
$server->add_signature_method(new OAuth\OAuthSignatureMethod_HMAC_SHA256());
Is there a way to configure ToolProvider to accept this signature method?
Thanks,
Mario
The text was updated successfully, but these errors were encountered: