Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Uptake APKAM feature [atWavi] #262

Open
sitaram-kalluri opened this issue Dec 11, 2023 · 1 comment
Open

Uptake APKAM feature [atWavi] #262

sitaram-kalluri opened this issue Dec 11, 2023 · 1 comment
Assignees
@Sardar1208 @sachins-geekyants @Dariamarg

Comments

@sitaram-kalluri
Copy link
Member

Is your feature request related to a problem? Please describe.

APKAM feature enables to authenticate an atSign specific to a mobile app. The .atKeys file generated is specific to the app and also enables access (read/write) based on the apps namespace.

For more details refer: https://github.com/atsign-foundation/at_protocol/blob/trunk/decisions/2023-01-pkam-per-app-and-device.md

Describe the solution you'd like

A sample demo enrollment app is available in https://github.com/atsign-foundation/at_widgets/tree/at_enrollment_app
@ksanty ksanty changed the title Uptake APKAM feature. Uptake APKAM feature [atWavi] Dec 11, 2023
@Sardar1208
Copy link
Contributor

moving to next sprint

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Sardar1208 Sardar1208

@sachins-geekyants sachins-geekyants

@Dariamarg Dariamarg

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@sitaram-kalluri @Sardar1208 @sachins-geekyants @Dariamarg