Hello David,

These are the instructions from the Admin Guide. Where exactly are these instructions wrong? We have no reports of this being broken anywhere else:

MessageBird
To configure SMS sender settings for MessageBird service, perform the following steps:
1 Select MessageBird in Sender service.
2 Recipient Mask: Specify the masked value that you want to display for the SMS.
The SMS OTP of the users is masked when users authenticate with the SMS OTP method.
NOTE: The default value is set and if you do not change the Recipient Mask value, the default
value is considered for masking of the SMS OTP.
3 Specify the Username, Password, and Sender name.
For more information, see the MessageBird website.
You can test the configurations for the SMS sender policy in the Test section.
1 Specify the phone number in Phone to which you want to send the SMS OTP.
2 Specify a message to be sent to the phone in Message.
3 Click Send test message!.
4 Click Save.
Real messaging uses async sender. Ensure that you have configured a chain with the SMS
method and assigned it to an event. Then sign-in to the Self-Service portal and test the SMS
authenticator. If it does not work, see the async logs.

I can see you have already an open ticket with Support, have you shared the current configuration with them?

Thanks.

Regards,

Luciano Testa

Many thanks for the Response, however here are my concerns.

Point 1 is exactly as you describe.

Point 2 I am seeing no mention of Recipient mask anywhere is the Messagebird Sender Configuration.

Point 3 User and password are set to the same values used when accessing the portal. The sender name is also correct. The sender name is correct since it works in a curl command and sends the sms correctly. All curl examples require an API Key and not a username and password as per the Messagebird configuration in AA.

It looks like the API has changed for messagebird but I can see no NETIQ reference to this just that it is supported.

Any thoughts on this  and many thanks.

Hello David,

I understand. I will check this with Development to confirm any changes and how to properly configure this.

Thanks.

Regards,

Luciano Testa

Hello David,

I have a question for you, are you using the MessageBird API v2 or v1?

The API v2 is not supported. Does this work if you activate the API v1?

Thanks.

Regards,

Luciano Testa

It is good that  you have confirmed my thoughts not he matter. Messagebird does not allow new users to use V1 of the API. Do you have any timescale on NetIQ supporting V2 ?

Many thanks for your answer

David

As an aside this would be good to be added to the documentation since it is currently wrong even for the API V1 integration.

Hello David,

No, we do not have such information, sorry.  My advice is to create a new entry in the Idea Exchange section of this forum requesting such change so Product Management can see it and act on it.

About the documentation, it was on it until 6.3, I am not sure why it was removed but I will add a note and ask PM about it.

Thanks.

Regards,

Luciano Testa