Hello,
we are about to release some apps via the FLP were the employee should logon by using two-
factor authentication (PWD&OTP) over an identity provider (as java).
Current State:
The above scenario is technically working. The user can authenticate
with the OTP generated on an mobile device, but that's not our
preferred way of delivering the OTP. It should be SMS.
SMS-Problem:
For sending SMS via HTTPS we stored an SSL certificate of the sms-
gateway provider in the as java identity provider. Additionally we
created a new HTTP Destination to the SMS-Gateway
location by referring to the SSL certificate and delivering basic
authentication. This all authentication and certificate is working,
if we provide the required URL-Parameters right in the field of the
destination URL and use the "Ping" function.
Here is the problem. The SMS-gateway needs some defined URL
parameters to work. They are "key=", "message=" and "to=". Wether in
the NWA>Destination UI nor in the OTPADMIN UI it is possible to map
the generated Message with passcode to the right URL Parameter which
is required by the SMS-gateway.
The HTTP API Documentation for the SMS-Gateway you find here
If this is a specific problem with this special provider, maybe you
can provide another one, which does not have this special
requirements. Maybe there is a workaround possible with some development on the java side.
Best regards,
Julian Branahl