Muralidharan

Manually test and close in this, if end2end test is not feasible

@gkc @cpswan Rough high level flow of what has to be accomplished. https://drive.google.com/file/d/1QnVYhGrxVDPK5ZFUMdwSCuKrkdcrYrEA/view?usp=sharing we can discuss in the call today

> @gkc @cpswan Rough high level flow of what has to be accomplished. https://drive.google.com/file/d/1QnVYhGrxVDPK5ZFUMdwSCuKrkdcrYrEA/view?usp=sharing we can discuss in the call today * sign data in zariot SIM. Verify the signature...

@cconstab @cpswan @gkc Please review the below steps for signing from response in SIM card and verifying the signature using ECC public key. 1. Generate sha256 digest of from response...

@gkc there has to be a change in server code. Based on metadata in the pkam public key (RSA or ECDSA) we should choose the verify signature algorithm(RSA or ECDSA)....

design document - in progress https://docs.google.com/document/d/1m0e0fg4hW3tKZxG9vVlz2eYw2frBkhEKwAoSDvxijgI/edit

Burnt 4 SP in sprint PR 55. Carrying over.

Implementation in progress https://github.com/atsign-foundation/at_client_sdk/pull/935

No progress in PR 57 since the focus was on onboarding_cli integration

@purnimavenkatasubbu Please test and document the code flow in at_onboarding_flutter/at_client_service for these scenarios 1. new atsign activation 2. user saved the .atKeys file and login to a different app on...