Using SMS and Email gateways

Even though Secfense User Access Security Broker does allow you to use emails and short text messages as a mean to deliver second factor codes it does not act as an email client or a cellphone.

Secfense Broker needs to use an API of an existing email or sms gateway to be able to send those messages.

In short - there is no general way to configure those gateways - you need to verify the configuration with the documentation delivered by the gateway provider and craft Headers and Payload accordingly and test frequently to make sure the messages arrive as expected.

There are two variables however that are required to craft a payload that would be accept both a user identifier (email or phone number) and a token used as a sencond factor.

Those variables are being refferenced with these strings:

{EMAIL} and {NUMBER} respectively for users email address and phone number {CODE} for a one time code that would be used as a second factor.

Those variables need to fit within the payload part of the message, just like in this example:

{"from":"Secfense", "to":"{NUMBER}", "mxessage":"Twoj jednorazowy kod: {CODE}", "format":"json", "fast":"1"}