Hi Chiu
I was thinking that the Server processing part would be done as part of Comfigurator and as far as the user is concerned it would be transparent. Would work like this:
(1) Setup Comfigurator to use a certificate.
(2) Setup is via normal \"User Codes\" section. User would type in the normal 4 digit code and in Comfigurator code you would ALSO create and encrypted version.
(3) Both the encrypted version and clear text version would be uploaded to Comfort with the configuration.
(4) Users could continue to logon via the 4 digit code for existing functionality.
(5) From an applications perspective we also setup with the same certificate and could use the encrypted one only \"IF\" it exists (I say IF because I realise here that if users changes their code via the keypad then there wouldnt be an encrypted version) if you supply a locked DLL or something) that apps (and ours
) can use.
That was my thought process. Would have thought the demands on teh UCM here would be quite light.
Regards
Julian
I was thinking that the Server processing part would be done as part of Comfigurator and as far as the user is concerned it would be transparent. Would work like this:
(1) Setup Comfigurator to use a certificate.
(2) Setup is via normal \"User Codes\" section. User would type in the normal 4 digit code and in Comfigurator code you would ALSO create and encrypted version.
(3) Both the encrypted version and clear text version would be uploaded to Comfort with the configuration.
(4) Users could continue to logon via the 4 digit code for existing functionality.
(5) From an applications perspective we also setup with the same certificate and could use the encrypted one only \"IF\" it exists (I say IF because I realise here that if users changes their code via the keypad then there wouldnt be an encrypted version) if you supply a locked DLL or something) that apps (and ours
) can use.That was my thought process. Would have thought the demands on teh UCM here would be quite light.
Regards
Julian