2.3 Terminology
The MyID documentation set uses the following terminology:
Term |
Description |
---|---|
A person who is responsible for the configuration and maintenance of MyID. |
|
A small program stored on a card and used to communicate directly with other systems or to process information. |
|
Hardware connected to a computer that can read and write the information stored on a smart card. |
|
A collective term for smart cards and tokens when there is no need to distinguish between them. |
|
A person who has been issued a card or other credentials. |
|
Workflows are combined into related sets called categories. Note: The term ‘group’ is not used as this has a distinct meaning within MyID. |
|
Proof of identity issued by a certification authority – this may be used to sign or encrypt information. |
|
The collective term for cards and tokens issued to a holder or a device. |
|
A piece of equipment – a PC, server, router, cell phone or other hardware. |
|
The information displayed during a stage. A form may consist of a single or multiple pages. |
|
Groups provide the structures that contain the people in the database. |
|
A queued task carried out by MyID. |
|
A person who uses MyID to issue and manage smart cards or tokens, but who is not responsible for configuration. |
|
A smart card printer – some printers also incorporate card readers. |
|
A plastic card that can store information using a chip, a contactless chip, a magnetic stripe, or a combination. |
|
A step within a workflow. |
|
Credentials using smart card technology in a different form that are used to hold identification details. For example, a USB token. A token may also refer to a one-time password software token. |
|
A secure cryptographic processor that may be installed in a variety of computing devices. Located on a device. |
|
Microsoft virtual smart card. A container that can hold credentials such as certificates and cryptographic keys. Stored on a trusted platform module. |
|
A sequence of web pages forming a task within MyID. |