Var ctxOTPFormatted = new Attribute("-formatted", "", otpFormatted) Set the formatted OTP into STS Universal User context attributes. Var ctxOTPHint = new Attribute("-hint", "", otpHint) Set the OTP hint into STS Universal User context attributes. the user together with the OTP as formatted OTP. OTP hint is data used to inform the user the OTP that the user must submit. Var otp = stsuuCtxAttrs.getAttributeValueByNameAndType("", "") Get the OTP generated by the OTP Provider plug-in. and rsa_otp, do not deliver the OTP to the user. Other OTP types, such as hotp_otp, hotp_otp, If the OTP type is mac_otp, then generate the OTP hint and the formatted OTP. Var otpType = stsuuCtxAttrs.getAttributeValueByNameAndType("-type", "") Get the OTP type selected by the user. Var stsuuCtxAttrs = stsuu.getContextAttributesAttributeContainer() Get the STS Universal User context attributes. This adds this selection in the UI, which will use the mac_otp mechanism to generate the OTP, but it won’t deliver it using any of the standard mechanisms, since we have declared it to “no_delivery”.Ģ) Then we look for this to come through the OTPDeliver Mapping rule, and just use the Javascript REST client to call something:Ī) Add some imports to the top of the mapping rule,ī) In the mac_otp type, see if they are delivering it to our specified attribute starting with RESTto:// Var destAttribute = "RESTto://somedestination" I also use it in the OTPDeliver mapping rule to determine if this mechanism This is an attribute that will show on the template page by default. To add a custom mechanism to the ISAM OTP framework, you just need to edit two OTP Mapping rule files:ġ) The OTPGetMethods Mapping rule add the new custom rest mechanism – you should see where it has the list: In this example – I tested it with Boxcar – an iOS App that lets you send Push notifications with a simple REST call. I wanted to make a new OTP Mechanism that was called by a JavaScript REST call – that wasn’t the SMS mechanism in the box.
0 kommentar(er)
