concepts:02-identity-proofing
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
concepts:02-identity-proofing [2019/08/01 09:39] tjotov created |
concepts:02-identity-proofing [2020/03/28 09:03] (current) mpospisek ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Identity proofing ====== | ====== Identity proofing ====== | ||
| - | ADUCID provides authentication. | + | ADUCID provides authentication. |
| + | * PEIG is identified | ||
| + | * PEIG recognizes the particular AIM | ||
| - | PEIG is assigned to a user account using primary key called " | + | <WRAP info> |
| - | + | * PEIG is assigned to a user account using primary key called " | |
| - | Proofing process assigns UDI to a real person | + | |
| + | * UDI can be generated or it can be anything service provider wants, e.g. email or login name. | ||
| + | </ | ||
| ===== Proofing scenarios ===== | ===== Proofing scenarios ===== | ||
| - | Thera are several ways how to proof a user. He/she can get to an office, show ID and get proofed. Or he/ she can be visited by person how can verify his / her identity. Or user can fill in a form, send it with a copy of her / his ID. | + | There are several ways, how to proof a user. |
| + | * He/she can get to an office, show ID and get proofed. | ||
| + | * Or he/ she can be visited by person how can verify his / her identity. | ||
| + | * Or user can fill in a form, send it with a copy of her / his ID. | ||
| 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. | ||
| Line 17: | Line 24: | ||
| ==== Activation code ==== | ==== Activation code ==== | ||
| - | User goes to an office and meets an administrator. Administrator fills in user details, verifies his / her ID. As result he gives / sends him an activation code. | + | * User goes to an office and meets an administrator. |
| + | * Administrator fills in user details, verifies his / her ID. | ||
| + | * As result he gives / sends him an activation code. | ||
| Using this code user can finish the proofing process by providing it to proofing application. | Using this code user can finish the proofing process by providing it to proofing application. | ||
| Line 23: | Line 32: | ||
| ==== Registration form ==== | ==== Registration form ==== | ||
| - | In this scenario | + | 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. | ||
| - | See also [[settings: | + | See also [[settings-mgmt:02-management-apps|Management Apps]] |
| Line 35: | Line 46: | ||
| For No-Code it is just a role called " | For No-Code it is just a role called " | ||
| + | <sxh bash> | ||
| < | < | ||
| Require valid-user | Require valid-user | ||
| Require role aducid: APPROVED | Require role aducid: APPROVED | ||
| </ | </ | ||
| + | </ | ||
| For development integration | For development integration | ||
| Line 46: | Line 58: | ||
| ADUCID UserAdmin application shows current proofing status of a particular user. | ADUCID UserAdmin application shows current proofing status of a particular user. | ||
| + | [<> | ||
concepts/02-identity-proofing.1564652366.txt.gz · Last modified: 2019/08/01 09:39 by tjotov
Page Tools
