Each April Tag can provide 512 unique values. If you need more than 512 unique values, (e.g. you have 1,000 employees) then you can use combinations of multiple April Tags to create more than 512 unique values. This page describes how to do that.


SAFR assumes everyone is given the same number of badges, and you can use n-factor auth to define how many badges are assigned to each person.  

Further, you need to make sure that every person is assigned a unique combination of N badges with digits in any order.   SeeCalculating+Number+of+April+Tags+Combinations which describes how the number of unique badges are determined.


As an example, assume there were only 2 unique April tag values (there are actually 512).  Then if you used 2 badges you could only choose following combinations:


1 + 1

1 + 2 (which is same as 2+1)

2 + 2


So SAFR interprets 1 + 2 the same as 2 + 1. 


Thru the process of n-factor auth, SAFR can validate that all the April codes that are associated with a person appear in the camera view at the same time the person's face is in view and that no other April codes are present. Handling+No+Match+with+Badges+in+SAFR+Actions describes quite well how this is done.


Note: You should consider using min required badge size in detector settings to make sure that someone else is not wearing or holding up a badge in the background.  If there are more badges than expected, SAFR may analyze the wrong badges first and incorrectly reject the person presenting the correct combination of badges. 


Its worth noting that holding up a large number of badges is not a viable attach vector.  SAFR will read the 1st N it finds and those must be the right combination.  It does not look for the combination its requires amongst the full list.  The first badge that is not in the required set will result in failure in processing.


Notes:


Its worth noting that there are other badge types.  I've been unable to get information from anyone in dev team about the other types and Internet searches have gotten nowhere (maybe they should have been called unicorn tags ;).  Mark has an item in his Todo list to chase down info on these.  My guess is, like April tags, they also offer a limited number of combinations.






Example:


  • set people's Moniker include 2 unique April tag values: 
  • Set nfactor in SAFRActions.conig



check ares.log, 522 12 or 12 522 can both work:


1. 12 522

    --> 2020-06-10 15:04:56 1.05sec id: d66b9637-21df-433a-99f2-9e3af30c392f x280 Logitech BRIO admin William u -> @nFactorStart unlock


    <-- 2020-06-10 15:04:57 Reply true 1.0 Please show your TagID 


    --> 2020-06-10 15:04:58 0.37sec id: 0b5e373b-99ba-4a65-9ec4-f48a7d58f2ce x280 Logitech BRIO -> @nFactorResolve unlock moniker|12


    nFactorResolve: 1


    --> 2020-06-10 15:04:58 0.80sec id: 354bd8f8-4cca-4739-a00b-45bb227c9633 x280 Logitech BRIO -> @nFactorResolve unlock moniker|522


    nFactorResolve: 0 python C:\ProgramData\RealNetworks\SAFR\ares\config\relay-lcus.py 1 -p COM3;


1. 522 12

    --> 2020-06-10 15:04:39 1.07sec id: 7d2fa0f7-6e5e-4866-9f34-f29ed824bbd1 x280 Logitech BRIO admin William u -> @nFactorStart unlock


    <-- 2020-06-10 15:04:40 Reply true 1.0 Please show your TagID 


    XXX 2020-06-10 15:04:39 1.69sec id: 7d2fa0f7-6e5e-4866-9f34-f29ed824bbd1 x280 Logitech BRIO admin William u


    --> 2020-06-10 15:04:41 0.39sec id: c77bbcaa-68b5-4f8e-8793-15600f9a1150 x280 Logitech BRIO -> @nFactorResolve unlock moniker|522


    nFactorResolve: 1


    --> 2020-06-10 15:04:41 0.51sec id: 7818367d-a3e0-4cb9-878e-0ea3374a0c01 x280 Logitech BRIO -> @nFactorResolve unlock moniker|12


    nFactorResolve: 0 python C:\ProgramData\RealNetworks\SAFR\ares\config\relay-lcus.py 1 -p COM3;


  • use 4 April Tag can create a tag like QR code.