ovh / ovh/docs

Invalid Signature OVH' s SMS

Open
#446 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
273
Forks
391
Avg merge
1m
Merged PRs (30d)
1

Description

I am trying to send SMS using OVH'SMS service , following this docs.

when i test the send with post methode for the url https://eu.api.ovh.com/1.0/sms/sms-zj16668-1/jobs

i get an

errorCode:INVALID_SIGNATURE

the signature is calculated as below :

        String signature = "$1$" + HashSHA1(AS + "+" + CK + "+" + METHOD + "+" + QUERY + "+" + BODY + "+" + TSTAMP);

with Get method(no Body) i get a successful result , however when i change to use a Post method with a Body ,the above error is triggered.

this is the Body i pass to signature :

        string BODY = @"{  ""receivers"": [ ""+33601020304"" ], ""message"": ""Test SMS OVH"", ""senderForResponse"": true}";

what i m doing wrong ?

#update
i found in the ovh community a similar issue and the solution where to use TLS1.2 PROTOCOL , however even after adding this proposed line of code:

 ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls | (SecurityProtocolType)768 | (SecurityProtocolType)3072;

I am still getting the same error ! ?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked OVH SMS API documentation and the POST endpoint shown in the report. Compare the documented signature inputs with the supplied C# request and body, then clarify the documentation so the POST example explains the required request details and avoids INVALID_SIGNATURE.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
api, documentation
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.