Forum Discussion
MichaelJordan_1
Nimbostratus
NimbostratusTrim Mobile Number
Hi
The SMS Company does not accept more than 10 caracters in http request as of MobileNumber. And also they don't accept these "+" sign or "+90". So it should look like "5431231020". This is the...
MichaelJordan_1Nimbostratus
NimbostratusHere is the working "Variable Assignment". Rule order is important!
- [S] session.logon.last.password = expr {[mcget{session.otp.assigned.val}]}
- session.logon.last.username = return [expr [string map {" " ""} [mcget {session.ad.last.attr.mobile}] ] ]
- session.logon.last.username = return [string range [mcget {session.logon.last.username}] end-9 end]
THiThink you don't want to assign the OTP value to session.logon.last.password before sending it out? The OTP value will be entered by the user at the logon page box, right after the http auth box where it is sent to SMS gateway, and it will be stored to session.logon.last.password variable and verified against the session.otp.assigned.val in the OTP Verify box.- MichaelJordan_1Yes, I have to do that before sending it out and it is. I just assign the otp value before HTTP-Auth object. Than I am asking the passcode after HTTP-Auth (if it is success) via "Logon Page"
- THiNow you are prepopulating the session.logon.last.password with the generated and correct OTP value (from session.otp.assigned.val). The user should enter it at the logon page and the the entered value should be compared with the session.otp.assigned.val for a match to allow proceeding in the flow. How have you defined the SMS gateway AAA server? Which session variable is sent to the mobile?
- MichaelJordan_1My problem is solved but I just want to add these answers; SMS Gw requests these variables in the URL: gsm test gsm should match mobile number and by default APM uses "session.logon.last.username" to send/replace text should match OTP message and by default APM uses "session.logon.last.password" to send/replace
