Hello Experts,
The customer is Whelen, and they reached out to us via Arrow, with the following questions:
1. The CA certificate generated by EdgeLock2GO has an expiration of 15 years from creation. I believe this is probably adequate for our use case, but I wanted to check whether it is possible to extend this.
2. In the past we used the transport lock on the A71CH to detect whether there was any tampering prior to first time use of the device. On that part, it was a latching mechanism. It appears the A5000 also has a transport lock but it is not a latching mechanism, but instead uses some type of authentication to lock/unlock the part. It wasn’t clear to me from the documentation exactly how this mechanism works or how the key is configured to use this mechanism. I am not sure whether this is something that can be configured through EdgeLock2GO or whether Arrow has the ability to configure this mechanism during programming.
Would you please help to advise?
Thanks in advance for any comment!
Best Regards,
Kan
1.I checked and found the same that currently there is no option to change validity of intermediate CA.
Basically,
1. you need to create authentication object like AES key, ec key or user id in se at 0x7FFF0200 RESERVED_ID_TRANSPORT (Edgelock2GO cannot provision this)
2. open authenticated session (any applet level session: aes , ec key or user id.)
3.setting lock (SetLockState APDU mentioned in AN13187)
Example I discussed above can help with usage of APIs and flow
PFA of the docs mentioned above