| (1.3.6.1.4.1.27630.2.1.1.62 DESC 'osiICardPPIDfriendly' ) |
osiICardPPIDfriendly attribute OID of openosi.schema for X500 / LDAP directory
Notation
This object identifier (OID) describes osiICardPPIDfriendly attribute of openosi.schema .
ASN1 notation: {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) openosi(27630) identification(2) schema(1) attribute(1) osiICardPPIDfriendly(62)}
URN notation: urn:oid:1.3.6.1.4.1.27630.2.1.1.62
IETF DOT notation: 1.3.6.1.4.1.27630.2.1.1.62
BNF notation (RFC822 Backus-Naur form): ( 1.3.6.1.4.1.27630.2.1.1.62 DESC 'osiICardPPIDfriendly' )
Description: osiICardPPIDfriendly attribute OID of openosi.schema for X500 / LDAP directory
Definition
osiICardPPIDfriendly attribute is a container for attributes types conforming with RFC4512 specification
.
DESC ' SHA1 hash of the site-specific PPID'
The PPID provides a site-specific (of relying party = web service) identifier for the user that is meaningful to the site and is suitable for programmatic processing. However, the PPID is not a good user-friendly identifier for an information card in customer-service situations in which users may have to convey their site-specific identities manually (for example, over the phone). It is difficult and cumbersome for a user to manually convey a PPID, which is a long case-sensitive (base64-encoded) string. We need an identifier for the card that makes sense to the user and is convenient. Furthermore, the identifier for the card should be consistent across a number of devices (multiple computers, telephones, and so on) to which the user carries the card.
The Site-Specific Card ID has the following characteristics:
- It is never carried inside tokens. It is only computed as a function of the site-specific PPID locally at either end.
- It is encoded as a 10-character alphanumeric string grouped into three groups separated by the 'hyphen' character in the form: AAA-AAAA-AAA (for example, the string "6QR-97A4-WR5"). Note that the hyphens are used for punctuation only.
- The encoding alphabet does NOT use the numbers '0' and '1' and the letters 'O' and 'I', to avoid confusion stemming from the similar glyphs used for these numbers and characters. This leaves 8 digits and 24 letters-a total of 32 alphanumeric symbols-as the alphabet for the encoding.
DESC ' SHA1 hash of the site-specific PPID without 0.1.o,i (XXX-XXXX-XXX )'
HashId = SHA1 hash of the site-specific PPID value
- Take the ith octet of HashId (denoted as HashId[i]).
- Find RawValue = HashId[i] % 32 (where % is the remainder operation).
- Ai = EncodedSymbol obtained by mapping RawValue to EncodedSymbol using the table that follows.
| Raw value |
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 |
30 |
31 |
| Encoded Symbol |
Q |
L |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
A |
B |
C |
D |
E |
F |
G |
H |
J |
K |
L |
M |
N |
P |
R |
S |
T |
U |
V |
X |
Y |
Z |
Syntax
attributetype (1.3.6.1.4.1.27630.2.1.1.62
NAME ( 'osiICardPPIDfriendly' 'icPPIDfriendly' )
DESC ' SHA1 hash of the site-specific PPID'
EQUALITY caseIgnoreMatch
SUBSTR caseIgnoreSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
Usage
It is mentionned by the following objectclasse:
For quick OID check (when registered) go to oid-info
and use the following syntax:
www.oid-info.com/get/<OID number>
OID XML format
<oid>
<asn1-notation>{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) openosi(27630) identification(2) schema(1) attribute(1) osiICardPPIDfriendly(62)}</asn1-notation>
<description>osiICardPPIDfriendly attributeOID of info card for openosi.schema for X500 / LDAP directory</description>
<information>More <i>information</i> can be found in <a href="http://openosi.org/osi/display/oid/1.3.6.1.4.1.27630.2.1.1.62">osiICardPPIDfriendly attributeOID of info card for openosi.schema for X500 / LDAP directory</a> </information>
</oid>