integration:authorization
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
integration:authorization [2019/08/01 08:27] tjotov |
integration:authorization [2019/08/01 08:36] (current) tjotov old revision restored (2019/08/01 08:27) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Authorization in No-code ====== | ||
| - | No-Code relies on Apache. You can use any authorization method on ADUCID Apache or ProxyPass to another Apache and resolve authorization there. | ||
| - | ADUCID security default application are authorized by Apache with group file authorization. It is recommended to used " | ||
| - | <sxh bash> | ||
| - | < | ||
| - | Require valid-user | ||
| - | Require group registrator | ||
| - | </ | ||
| - | </ | ||
| - | ===== ADUCID authorization attributes ===== | ||
| - | We add two atrribute sets to support Apache authorization: | ||
| - | You can force it using Require role aducid:XXX | ||
| - | <sxh bash> | ||
| - | < | ||
| - | Require valid-user | ||
| - | Require role aducid: | ||
| - | </ | ||
| - | </ | ||
| - | Personal factor states: | ||
| - | * PF_VERIFIED - personal factor has been verified | ||
| - | * CF_VERIFIED - comfort factor has been verified | ||
| - | * PF_MISSING - user has no PF/CF | ||
| - | |||
| - | Proofing states: | ||
| - | * APPROVED - user is proofed | ||
| - | * PROOFING_IN_PROGRESS – user proofing is running | ||
| - | * NO_PROOFING_STATUS – proofing did not start yet | ||
| - | |||
| - | PEIG type states: | ||
| - | * USER – PEIG is linked to user | ||
| - | * NO_PEIG_TYPE – PEIG type is unknown | ||
| - | * MACHINE (future IOT support - PEIG is linked to a machine) | ||
| - | |||
| - | |||
| - | |||
integration/authorization.1564648077.txt.gz · Last modified: 2019/08/01 08:27 by tjotov
Page Tools
