Package | Description |
---|---|
be.fedict.commons.eid.client |
eID client classes.
|
be.fedict.commons.eid.client.event |
Client listener interfaces.
|
be.fedict.commons.eid.client.spi |
Service provider interfaces.
|
Class and Description |
---|
BeIDCard
One BeIDCard instance represents one Belgian Electronic Identity Card,
physically present in a connected javax.smartcardio.CardTerminal.
|
BeIDCardManager
A BeIDCardManager uses a
CardAndTerminalManager to detect Card
Insertion and Removal Events, distinguishes between Belgian eID and other
cards, calls any registered BeIDCardEventsListeners for eID cards inserted
and removed, and any registered CardEventsListener for other cards being
inserted and removed. |
BeIDCards
BeIDCards is a synchronous approach to Belgian Identity Cards and their
presence in the user's system, as opposed to the asynchronous, event-driven
approach of
BeIDCardManager (but BeIDCards uses an underlying
BeIDCardManager to achieve it's goals). |
BeIDCardsException
BeIDCardsException groups all BeIDCard Event-related exceptions, so they can
be more conveniently thrown and caught
|
CancelledException
CancelledException is thrown when a method is blocking on a user action
through a UI, and the users declines to respond (e.g. by closing the
requesting dialog)
|
CardAndTerminalManager
A CardAndTerminalManager maintains an active state overview of all
javax.smartcardio.CardTerminal attached to a system's pcsc subsystem, and
notifies registered:
CardTerminalEventsListeners of any CardTerminals Attached or Detached
CardEventsListeners of any Cards inserted into or removed from any
attached CardTerminals
Note that at the level of CardAndTerminalManager there is no distinction
between types of cards or terminals: They are merely reported using the
standard javax.smartcardio classes.
|
CardAndTerminalManager.PROTOCOL |
FileType
The FileType enum encapsulates the fileID, keyID, and some usage parameters
about the files stored on an BeIDCard.
|
PINPurpose
a PINPurpose encapsulates the different reasons why the user's PIN code may
be requested: an authentication signature, a non-repudiation signature, or a
user-requested test of their PIN code.
|
Class and Description |
---|
BeIDCard
One BeIDCard instance represents one Belgian Electronic Identity Card,
physically present in a connected javax.smartcardio.CardTerminal.
|
FileType
The FileType enum encapsulates the fileID, keyID, and some usage parameters
about the files stored on an BeIDCard.
|
Class and Description |
---|
BeIDCard
One BeIDCard instance represents one Belgian Electronic Identity Card,
physically present in a connected javax.smartcardio.CardTerminal.
|
CancelledException
CancelledException is thrown when a method is blocking on a user action
through a UI, and the users declines to respond (e.g. by closing the
requesting dialog)
|
OutOfCardsException
OutOfCardsException is thrown by a UI when the last BeID card is removed
while it is attempting to let the user choose between several.
|
PINPurpose
a PINPurpose encapsulates the different reasons why the user's PIN code may
be requested: an authentication signature, a non-repudiation signature, or a
user-requested test of their PIN code.
|
Copyright © 2012–2024 e-Contract.be BV. All rights reserved.