Restriction of access Manager

[vishwanchandapu]

Hi,

While going through Restrictions of Access manager, we need help to understand more on below restriction of access manager.

"The Access Manager does not attempt to re-establish a broken connection to the SE05x. To recognize and recover from a broken connection, a system integrator must monitor failure to communicate to the Secure Element by the client processes. As and if required the Access Manager must be restarted and the affected client processes must reconnect to the Access Manager."

1. "Broken connection": what are scenarios this could happen?

2. "system integrator " does it mean we need have separate daemon just to monitor communication failures of clients?

3."Access Manager must be restarted" what is guarantee that restarting access Manager will fix the broken connection?

[vishwanchandapu]

Hi @michaelsalfer 

Thanks for the reply,

Thats means as long as if we restrict access of secure element only through " Access Manager" chances for communication breakdown is less.?

Regards

Vishwa

[Kan_Li · Accepted solution]

Hello @vishwanchandapu ,

Yes, your understanding is correct! When using the AM then, yes, the chance for breakdown for sure is much lower - as the AM was designed to prevent that.

Have a great day,
Kan

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

[michaelsalfer]

Hello,

a "broken connection" would happen when e.g. the access manager creates a secure session (PlatformSCP authentication) and then another process circumvents the access manager and sends a command to the SE. This would break the established secure channel (all commands are cryptographically chained) and the following communication would not succeed until a new authentication happens. Restarting the access manager re-authenticates the IC.

If there is a chance seen for accesses outside the access manager which may break the secure channel, then a client service which periodically tries to communicate over the access manager with the SE can detect any secure channel breakdown. 

Kind regards,
Michael