other:identity-proofing
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
other:identity-proofing [2019/08/01 09:23] tjotov created |
other:identity-proofing [2019/08/01 09:39] tjotov removed |
||
|---|---|---|---|
| Line 25: | Line 25: | ||
| In this scenario user fills in a form and sends it to registration point (scan of ID might be required). Then he/ she goes to the office, administrator verifies this form and approves the user. | In this scenario user fills in a form and sends it to registration point (scan of ID might be required). Then he/ she goes to the office, administrator verifies this form and approves the user. | ||
| - | ==== QR proofing - admin fills form, user scans ==== | ||
| - | As in first scenario a uses comes in an office and meets an administrator. But no activation code is created / sent. Instead user scans a QR code displayed on administrator’s PEIG. | + | See also [[settings: |
| - | |||
| - | ==== Identity link proofing ==== | ||
| - | |||
| - | If one AIM contains proofed identities, it can act as identity provider for other AIMs (this scenario must be enabled and supported by both sides). | ||
| Line 51: | Line 46: | ||
| ADUCID UserAdmin application shows current proofing status of a particular user. | ADUCID UserAdmin application shows current proofing status of a particular user. | ||
| - | See Javadoc and Tomcat adapter documentation for details. | ||
Page Tools
