Sidebar
developers:advanced-integration:result-operation-codes
This is an old revision of the document!
Error statuses of authentication process
| Code | Brief description | Note |
| OK | Success | Normal → normal success |
| KO | Failure | Normal → normal negative result |
| NAU | Disagreement at user side | Rejected by user - real or artificial because PEIG is temporarily blocked → normal authentication failure |
| PPNP | PEIG is not available | Functional problem - PEIG is not connected to PEIG-Proxy → Display to user (with instructions) |
| USP | Unknown service provider | Normal status - unknown user → management (initialization menu - init) |
| USSP | Unknown secondary service provider | Normal status - unknown user for secondary provider → management (explanatory text - link with other SP) |
| UU | Unknown user | Operating status or security problem - the identity obtained from PEIG does not exist in AIM → management - either it is an attack, or repair after AIM failure - reinit |
| UUS | Unknown user for secondary provider | Operation status or security problem - the identity does not exist in a secondary AIM → management - it is either the operation status, attack or repair after failure of AIM - init, or reinit at secondary AIM |
| UI | Invalid identification | Operation status - PEIG Operation status - PEIG or AIM determined that CyberID is violating terms of validity (time or number of uses) → management - e.g. rechange menu or change in access rights |
| UPR | Unsupported security profile | AIM or PEIG cannot find (accept) the requested security profile → change of profile or denial of PEIG |
| UIP | Unsupported IL security profile | AIM or PEIG cannot find (accept) the requested IL (identity link) security profile → change in IL profile or request denial |
| UOP | Unsupported extension object profile | PEIG cannot accept the required security profile of the extension object → change of profile or request denial |
| VI | Valid identity | Functional problem or security incident - CyberID is valid upon requirement for rechange → probable use of rechange |
| NEO | Non-existing extension object | Functional problem - request for non-existing object → probable application error |
| NTD | Nothing to do | Normal - nothing to apply the request to → normal behaviour - failure (e.g. reading an empty list of objects) - application error or normal operation status |
| SPE | Error of second PEIG | Security of functional problem - attack or operation status or user error |
| UTL | Unsupported transition between security levels | Cannot accept the required change in security profile → change of request or acceptance of unknown CyberID |
| DLN | Requested login name is already used by another PEIG | Functional problem - duplicity of legacy login name → probable error of application or application user |
| NER | Insufficient rights to process the request | Functional problem → application error or user problem |
| DR | Duplicate replica | Functional problem → application error or user problem |
| NS | Non-existing session | Functional problem → application error or user problem |
| CTO | Exceeded max. communication time | Functional problem → configuration error or operation problem |
| ERR | Unspecified error | Security of functional problem: attack or implementation error, standard, general error message instead of specific ones |
| UV | Unsupported version | Functional problem (incompatibility) → management - change of request |
| DI | Repeated initialization | Functional problem or security incident - PEIG identified an attempt at repeated origin of a CyberID for the same AIM → either an error in the application that did not check the existence of the CyberID, or a security attack or configuration error - another AIM exists with the same SPID |
| CR | Applying a rejected change | Recovery from problem - consequence |
| MI | Missing identity | Functional problem or security incident - CyberID does not exist upon request for reinit → probable incorrect use of reinit |
| IE | Self-termination | PEIG security compromised→ management of the compromise, e.g. flagging an attribute and blocking access rights |
| NAP | Not accepted by PEIG | Secondary error - use primary |
| UCC | Incompatible keys | Functional problem - problem with keys in extension object → probable application error |
| NOP | No operation requested | Functional problem or attack → probable application error |
| UIL | Unknown ILID | Functional problem or attack → probable application error |
| ILM | Missing ILID | Functional problem or attack → probable application error |
| ISE | Identity Link electronic stamp error | Functional problem or attack → probable application error |
| NSA | Missing address of secondary AIM | Functional problem or attack → probable application error |
| NU | Not unique | Internal alarm or functional or security problem |
| LI | Locked identity | Normal - identity removed from use by administrator or automatically → normal authentication failure |
| DMR | Duplicated meeting room | Normal—meeting room name conflict, the attempt to create a second meeting room with the same name results in a normal failure |
| UMR | Unknown meeting room | Normal—meeting room name conflict, the attempt to enter the non-existent meeting room results in a normal failure |
| CMR | Closed meeting room | Normal—the attempt to enter into a closed meeting room results in a normal failure |
| MET | Meeting room enter timeout | Normal—the second PEIG did not enter into the meeting room in time results in a normal failure |
| MCT | Meeting room confirmation timeout | Normal—the first PEIG did not confirm the second PEIG in time results in a normal failure |
| BIM | Binding item is missing | Security or functional problem—the required binding information is missing |
| BEE | Binding evaluation error | Security or functional problem—an attack to a banded channel or target application integration error |
| UBM | Unable binding mode | Security or functional problem—probably a target application integration error |
| MAD | MITM attacker detected | Security problem—the MITM attacker is recognised |
| BTO | Binding timeout | Normal—timeout in binding communication |
| PCD | PEIG copy detected | Security problem—the PEIG copy is recognised |
| ADM | Anti-copy data missing | Security or functional problem—probably an attack or internal error or HW error |
| AAF | AIM anti-copy failure | Normal—AIM tolerated storage failure has been recognised by anti-copy detection |
| PAF | PEIG anti-copy failure | Normal—PEIG tolerated storage failure has been recognised by anti-copy detection |
| ACI | Anti-copy check impossible | Security or functional problem—probably an attack or internal error |
| LLF | Locked local factor | Normal or Security problem— Local Factor is locked by time lock |
| ALF | Absent local factor | Normal – requested Local factor does not exist → normal behaviour - failure - application error or normal operation status |
| ULT | Unsupported local factor technology | Normal – the PEIG HW does not support requested Local factor → normal behaviour, user issue |
| DLI | Duplicated local factor init | Normal – repeated initialization of the Local factor → normal behaviour - failure - application error or normal operation status |
| ULF | Unverified local factor | Internal status |
| SLS | Successful local factor synchronization | Internal status |
| ICF | Integrity check failed | Security or functional problem—probably an attack or internal error |
| NTE | Network error | Normal—communication infrastructure error |
| SCE | Secondary communication error | Normal—communication infrastructure error |
| EOP | Empty original PEIG | Normal – the source (primary) PEIG in is empty → normal behaviour - failure - user or application error or normal operation status |
| URM | Unsupported replica mode | Normal – requested replica is not possible → normal behaviour - failure - application error or normal operation status |
| BLR | Blocked Replica | Normal or security problem – requested replica was blocked → normal behaviour - failure - user error or attack |
| LFM | Local Factor merge | Internal status |
| COR | Confirmed Replica | Internal status |
| WFC | Waiting for confirmation | Internal status |
| DLV | Do Local Factor verification | Internal status |
| MRR | Meeting Room Ready | Internal status |
| WBK | Waiting for Binding Key | Internal status |
| HCM | HW Check item missing in auth vector | Security or functional problem—probably an attack or internal error or HW error |
| HCD | PEIG HW change detected | Security problem—the PEIG hardware change is recognised |
| SUV | Secondary (system) Unsupported Version | Normal – Secondary AIM version is old and it is not supported. |
| OPV | Old Peig Version | Normal – the PEIG version is old and do not support requested functionality |
| USF | Unsupported Feature | Normal – the requested features set is not supported |
| INR | Insufficient rights | Administration/proofing – you have insufficient rights to access an operation |
| DNF | Data not found | Administration/proofing – requested data not found on AIM |
| DAE | Data already exists | Administration/proofing – requested data already exists on AIM |
| CNF | Code not found | Administration/proofing – requested activation code not found on AIM |
| FNF | Form not found | Administration/proofing – requested form identifier not found on AIM |
developers/advanced-integration/result-operation-codes.1477468112.txt.gz · Last modified: 2016/10/26 07:48 by 127.0.0.1
