You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The purpose is to give the user something to play with and edit, in order to understand what-is-what in the beginning. Possible use cases are:
Proof of organization membership: by entering user and password, the users get a credential stating they are member of that org, expiring after 6 months
Voucher/ticket: users are sent per email/chat a 6 chars/digits randomize (or not) voucher, by entering it in the authz-server page, they get a credential called "Event ticket" or something similar. Upon verification voucher you should be "burned", making it usable only once. Ideally an array of 50 random vouchers should be generated when creating the org - if it's too much hassle we can reuse the same 50 for every org (or we can generate 10.000 and pick 50 randomly).
Proof of email possession (Verification only): this is paired with with the credential already offered by our organization "DIDroom", that offers a proof of verified email to all the users that sign up and verify their email
The text was updated successfully, but these errors were encountered:
andrea-dintino
changed the title
[Maybe duplicate] when new organization is created, create 2-3 demo issuance/verification flows
Seeds - [Maybe duplicate] when new organization is created, create 2-3 demo issuance/verification flows
Feb 1, 2025
The purpose is to give the user something to play with and edit, in order to understand what-is-what in the beginning. Possible use cases are:
Proof of organization membership: by entering user and password, the users get a credential stating they are member of that org, expiring after 6 months
Voucher/ticket: users are sent per email/chat a 6 chars/digits randomize (or not) voucher, by entering it in the authz-server page, they get a credential called "Event ticket" or something similar. Upon verification voucher you should be "burned", making it usable only once. Ideally an array of 50 random vouchers should be generated when creating the org - if it's too much hassle we can reuse the same 50 for every org (or we can generate 10.000 and pick 50 randomly).
Proof of email possession (Verification only): this is paired with with the credential already offered by our organization "DIDroom", that offers a proof of verified email to all the users that sign up and verify their email
The text was updated successfully, but these errors were encountered: