APKAM: Onboarding Widget Updates

[XavierChanth]

Standalone Widget which can optionally be included in the onboarding widget:

Requesting App

Beta Give feedback

1. Input for OTP
2. Enroll App / Request enrollment button
3. Enrollment request status

Standalone widget for approving side

Receiving App

Beta Give feedback

1. List existing requests
2. Approve / Deny any request
3. Generate & Display pin

Blocking: atsign-foundation/noports#163

[gkc]

Added this ticket to our main project sprint planning board. Set as P0 as it needs to get started during this sprint. Needs to be estimated at planning poker.

[sitaram-kalluri]

@CurtlyCritchlow : The APKAM changes in at_client SDK are in srk_apkam_changes

[murali-shris]

@CurtlyCritchlow please update this task with the progress

[CurtlyCritchlow]

_

[CurtlyCritchlow]

I built the APKAM Request widget but I got stuck trying connect to vip.ve.atsign.zone. The production server doesn't have the necessary code changes as yet. @sitaram-kalluri and @murali-shris are helping me get unblock.

[sitaram-kalluri]

Spent 5 SP in PR-68.
Completed implementation of APKAM-UI for the following
In receiving app:

• notification screen to receive the enrollment notifications
• Approve/Deny Notifications
• Generate and display OTP
  In requesting app:
• Send request for enrollment
• List enrollments.

The changes are available in https://github.com/atsign-foundation/at_widgets/tree/at_enrollment_service

[gkc]

@CurtlyCritchlow @sitaram-kalluri @murali-shris what's latest status on this?

[sitaram-kalluri]

@gkc: The demo app we have currently is functionally working:

• An enrollment screen to submit an enrollment request.
• Notifications screen which display the enrollment requests. Approve or deny the enrollment request.
• A widget to display the OTP.
• Upon approving the enrollment, on the app that has submitted the enrollment, a .atKeys file is generated with APKAM keys and user can successfully login with the APKAM .atKeys file.

[gkc]

Thank you @sitaram-kalluri

Are these available as widgets? Is there documentation? How would I (1) build an app which handles enrollment requests (list enrollments, generate OTPs, receive enrollment request notifications and approve or deny them (2) build an app which can make an enrollment request, and complete enrollment if approved?

[sitaram-kalluri]

Thank you @sitaram-kalluri

Are these available as widgets? Is there documentation? How would I (1) build an app which handles enrollment requests (list enrollments, generate OTPs, receive enrollment request notifications and approve or deny them (2) build an app which can make an enrollment request, and complete enrollment if approved?

@gkc: Yes, the above functionality is available as widgets. Updated the README of the at_enrollment_app package on how to use it.

Attaching the README link here:README

[gkc]

Thanks @sitaram-kalluri

[sitaram-kalluri]

Attaching the screenshots of the the demo app developed for enrollment service

Screenshots of the demo enrollment service

[ksanty]

@sachins-geekyants @Sardar1208 tasks to be defined for the apps team. @murali-shris will clarify further

[Sardar1208]

@sachins-geekyants Has completed the the UI according to the design. Currently working on the integration of services.
Minor blocker due to unsupported feature on iOS

[Sardar1208]

Reducing to 6 SP and moving to next sprint

[Sardar1208]

Needs more work. Keeping the 6SP and moving to next sprint

[Sardar1208]

Needs more work
moving to next sprint.

[sachins-geekyants]

apkam keychain store migrated from flutter_secure_storage to biometric_storage : apkam_onboarding_biometric_storage

[sachins-geekyants]

Currently, we have two dependencies on sdk

• encryptedAPKAMSymmetric key is missed when the pending enrollments are fetched

• on enrollment approval, there is no way of knowing the path where atKey have been saved

cc: @sitaram-kalluri

[sitaram-kalluri]

Currently, we have two dependencies on sdk

* [encryptedAPKAMSymmetric key is missed when the pending enrollments are fetched](https://github.com/atsign-foundation/at_server/issues/1821)

* on enrollment approval, there is no way of knowing the path where atKey have been saved

cc: @sitaram-kalluri

encryptedAPKAMSymmetric key is missed when the pending enrollments are fetched : This is completed and changes are deployed to canary.

We are working on 2nd issue.

[gkc]

@sitaram-kalluri Have you done sanity testing with any of the canary atSigns? If it's safe to promote this from canary to prod then we should do that without much delay.

[sitaram-kalluri]

@sitaram-kalluri Have you done sanity testing with any of the canary atSigns? If it's safe to promote this from canary to prod then we should do that without much delay.

@gkc : Purnima is running sanity tests on the canary atSigns.

[sitaram-kalluri]

Currently, we have two dependencies on sdk

* [encryptedAPKAMSymmetric key is missed when the pending enrollments are fetched](https://github.com/atsign-foundation/at_server/issues/1821)

* on enrollment approval, there is no way of knowing the path where atKey have been saved

cc: @sitaram-kalluri

The second issue is addressed in the PR: atsign-foundation/at_client_sdk#1257

[sachins-geekyants]

We have a working version of enrollment package.

Work that still needs to be done

- fetchPendingEnrollments gives denied/approved requests.
- use the generated atkey to automatically onboard
- docs

[sitaram-kalluri]

We have a working version of enrollment demo app which is available in the following branch: https://github.com/atsign-foundation/at_widgets/tree/enrollment_screens .

Pending work is to merge the changes into trunk branch and publish the packages. We have a tracker ticket on the pending action items: https://github.com/atsign-foundation/operations/issues/88

Closing this ticket here.