UIC Bezel5 Programmer’s Manual
Page.120/166
UDN PM098 Rev. 1.0
Copyright © 2013, Uniform Industrial Corp. All Rights Reserved
Authentication involved entities:
1.
The claimant = the host application
2.
The verifier = the reader
3.
TEXT = the command/or key data to be sent from the host to the reader
4.
PrivA = The RSA private key at the host application
5.
PubA = The RSA public key at the reader
6.
TDES/RSA […] = Data encrypted either by RSA or Triple DES
The authentication process proceeds as follows:
1.
The claimant makes an authentication request to the verifier.
2.
The verifier generates a random number challenge R
B
(16 bytes data generated by the true
random number generator).
3.
The verifier encrypts R
B
and its SHA1 value, Pub
A
[R
B
|| SHA1(R
B
)] and sends to the claimant.
4.
Upon receiving the challenge, the claimant decrypts R
B
and validates SHA1 value. If SHA1
fails, the claimant terminates the process or requests R
B
again.
5.
The claimant creates an authentication token, TokenAB, by concatenating data and
generating a digital signature:
TokenAB = Priv
A
-
RSA
[ R
B
|| TEXT ||SHA1(R
B
||TEXT)]
6.
The claimant sends the TokenAB to the verifier.
7.
The verifier decrypts the TEXT and retrieves the SHA1 value by using the public RSA key,
Pub
A
.
8.
The verifier executes the command data in [TEXT] if the signature is validated OK.
The R
B
must be used only once to enter the administration mode of the reader.
Device challenge
PubA
[ R
B
||SHA1(R
B
)]
Authentication Token
TokenAB =
PrivA-RSA
[ R
B
|| TEXT || SHA1( R
B
||TEXT )]
Acknowledge if successful
Requires authentication
