Enroll sms token type via API (token/init)

bristoldev · April 27, 2020, 1:02pm

Hello

I am trying to use the API to enroll an sms token to a user. I have been using the dotnet provider found here:

sbidy/privacyIDEA_dotnetProvider/blob/master/OTPprovider.cs

using System;
using System.Collections.Generic;
using System.Collections.Specialized;
using System.Diagnostics;
using System.IO;
using System.Linq;
using System.Net;
using System.Text;
using System.Text.RegularExpressions;

namespace privacyIDEAprovider
{
    public class OTPprovider
    {
        private string URL;
        /// <summary>
        /// Class creates a OTPprovide for the privacyIDEA system
        /// </summary>
        /// <param name="privacyIDEAurl">Provide the URL (HTTPS) to the privacyIDEA system</param>
        public OTPprovider(string privacyIDEAurl)

This file has been truncated. show original

Whenever I call enrollSMSToken which is mapped to /token/init the token created when I view via the admin UI is not type sms but type HOTP.

I POST to /token/init?genkey=1 and supply the following parameters:

                    {"type ", "sms"},
                    {"user", OTPuser},
                    {"realm", realm},
                    {"phone", phonenumber}

I cannot find phone on the list of parameters here in the docs for token/init so wonder if I am not passing the right/required parameters:

I was wondering where I can find an example of using the API to enroll sms tokens?

Thanks

cornelinux · April 27, 2020, 7:53pm

I do not know, if this code you mentioned works.

You can enroll an SMS token by issuing a POST request with the parameters

genkey=1
type=sms
phone=phonenumber

See https://privacyidea.readthedocs.io/en/latest/modules/api/token.html#post--token-init
Maybe you want to checkout outside of this code.

bristoldev · April 27, 2020, 9:18pm

Many thanks for the prompt response.

So I tried a POST request with those 3 parameters but the token created is still of type hotp. I can create type sms via the UI without a problem.

I have configured Twilio as an SMS Gateway I wondered if there is anything else that could be causing this to happen?

Thank you

cornelinux · April 27, 2020, 9:27pm

Open the developer mode of your browser.
Create an SMS token in the WebUI
…and what the POST request.

I suspect that your client, which you are using trying to issuing the request, is broken.