Use One Time Password (OTP) in External Apps

this topic describes registering and viewing offline token in an external application using kron pam currently, users can view offline token in the kron pam mobile application however, some customers request to view offline token in their own apps standards standard 1 kron pam server and mobile application use totp (time based one time password algorithm) to create and view one time tokens the ietf rfc number is rfc 6238 see the rfc document for development on the mobile side standard 2 kron pam creates the qr codes according to the iso/iec 18004 2015 standards as such, you can either write the qr code and totp algorithms according to these standards or use any third party libraries supporting these standards kron pam otp parameters kron pam uses the following totp parameters algorithm sha1 digits 6 counter not used period 30 seconds secret obtained from the qr code when decoding the qr code, a key string is acquired it is a 36 character key you discard the first four characters and use the last 32 digits developing an offline token mechanism on a mobile application there are two main functions under this subject a registering the qr code the customers need to design a qr code scanning feature on their own mobile apps this feature should be compatible with standard 2, which is explained above when the qr code is scanned by the mobile app, the output string should be seen below 'otpauth //totp/single%20connect%20radius%20account%3aadmin%40kron com tr?secret=47hy4sra v74z72h07bqy53gdnjclqdwsjujv\&issuer=single%20connect%20radius%20account\&algorithmzsha1' then the mobile app should use and record this secret key into the mobile device b generating an offline token using the pre registered qr code the customers need to design an offline token generation feature on their own mobile apps this feature should be compatible with standard 1, which is explained above this feature should use the recorded secret key while generating the offline token with pam otp parameters use cases qr code registration kron pam admin sends qr codes to the users via email from the kron pam menu users scan the qr codes on the customer mobile app qr code registration screen mobile device records the qr codes offline token customer mobile user generates offline token on customer mobile application customer mobile user uses the offline token in the required business flows on kron pam support and maintenance in some cases, the mobile application user has to register the qr codes again when the user uses a new mobile device or loses the recorded secret key on the mobile device (during the mobile app updates), the user must re register the qr codes if the mobile user has the previous email that includes the qr code, the mobile user can use this code otherwise, kron pam admin may send a new email to the mobile user