Sitaram Pavan Kumar Kalluri

Work done in PR:73 - at_auth package changes are uptaken into the at_client_mobile and the changes are available in the [apkam_onboarding_changes](https://github.com/atsign-foundation/at_client_sdk/tree/apkam_onboarding_changes). Pending work in PR-74 : Review the code changes...

Spent 8 SP in PR-74 The enrollment changes that are common between the "at_onboarding_flutter" for UI and "at_onboarding_cli" are moved to AtAuth package. The corresponding changes in at_client_mobile are completed...

Spent 5 SP in PR-75. - Tested the changes with enrollment app. where the enrollment is being submitted and able to generate .keys file upon approval. - Pending work is...

Spent 3 SP in PR-76 - Tested the at_auth package changes with wavi app and buzz app and able to onboard the atsign successfully.

Published the at_auth package. at_auth v1.0.6 has the changes related to APKAM

The changes are completed and are merged to trunk branch in at_client_mobile in the PR: https://github.com/atsign-foundation/at_client_sdk/pull/1257. Hence closing the issue.

> @sitaram-kalluri If you're looking for what to pick up next, I'd suggest this one @gkc: Sure, I will start on this. Thank you.

Following are the scenarios with expected behaviour when starting atClient in offline mode: 1. When the network is down and atSign is onboarded, Should the user be notified that sync...

> Get a value from another atSign that has already been synch should be fine. Is that covered in get atKey? @cconstab: The value of the key that belongs to...

> Does this still need discussion or are we now in implementation? @gkc: We have a version of the implementation checked-in into [at_client_offline_access](https://github.com/atsign-foundation/at_client_sdk/tree/at_client_offline_access) branch in at_client_sdk. Following is the [link](https://github.com/atsign-foundation/at_client_sdk/compare/at_client_offline_access)...