documentation:identity-proofing
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
documentation:identity-proofing [2018/05/18 11:07] 10.144.24.34 old revision restored (2016/09/08 12:17) |
documentation:identity-proofing [2018/06/14 12:25] tjotov |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ADUCID provides authentication. It guarantees that PEIG is identified every single time by AIM and also PEIG always recognized particular AIM. | ADUCID provides authentication. It guarantees that PEIG is identified every single time by AIM and also PEIG always recognized particular AIM. | ||
| - | Target application which uses ADUCID authentication needs some key to bind authentication to its own user database. It might use AUDCID UID (User database index), e-mail or any other attribute. | + | PEIG is assigned |
| - | As result | + | Proofing process assigns UDI to a real person |
| - | + | ||
| - | This is only technical perspective of authentication. The most important issue for service provider is to know if that PEIG is owned by “right” person – or “proofed” person. This is accomplished by process called Identity proofing. | + | |
| ===== Proofing scenarios ===== | ===== Proofing scenarios ===== | ||
| Line 15: | Line 13: | ||
| To proof someone’s identity there has to be some administrator with right to verify and approve users. This administrator has to have role called “registrator” and has to be proofed and verified using personal factor. | To proof someone’s identity there has to be some administrator with right to verify and approve users. This administrator has to have role called “registrator” and has to be proofed and verified using personal factor. | ||
| - | ADUCID demonstrates and supports these basic scenarios: | + | ADUCID demonstrates and supports these scenarios: |
| ==== Activation code ==== | ==== Activation code ==== | ||
Page Tools
