Thanks. That is exactly what I'll do.
When I'm done implementing it, I will post in the forum the script to send SOAP requests.
This way anyone who needs it will be able to use it.
I'll likely user the Email version as the base for implementing this component, for sending/receiving the SOAP req.
It would be nice if ISAM had a way to create component by just importing the WSDL file, and generating the code...
------------------------------
Joao Goncalves
Pyxis, Lda.
Sintra
+351 91 721 4994
------------------------------
Original Message:
Sent: Thu April 22, 2021 06:03 AM
From: Jon Harry
Subject: SMS OTP
Joao,
The built-in SMS mechanism only supports making a simple REST call to send an SMS message. It is always a GET. You can specify the Query String parameters that get sent as part of configuration (default is from = +12345678, to = $DEST_NO$, message = $MSG$ ) and what return code/body indicates success (default is 201).
If you need to request SMS in a different way, you'll need a proxy to accept message in format above and then make the call out in whatever way is required by the SMS service. This could be implemented outside Verify Access but I know that other customers with this need have implemented this proxy as a custom authentication policy in AAC (using HTTP Client to make the outbound call to real SMS service).
Jon.
------------------------------
Jon Harry
Consulting IT Security Specialist
IBM
Original Message:
Sent: Wed April 21, 2021 02:47 PM
From: Joao Goncalves
Subject: SMS OTP
When configuring the SMS OTP, there are several parameters we may include.
Where can we find or change the body of the request?
In fact, to send an SMS, i will need to make a SOAP request. Where can I define the SOAP message, and use Macro (eventually) to fill the pieces as defined in the SMS OTP mechanism properties?
------------------------------
Joao Goncalves
Pyxis, Lda.
Sintra
+351 91 721 4994
------------------------------