Image Removed
Description
Alison-Desktop allows generation of keys and installation of certificates from an external application. It is designed to be accessed from a browser mainly.
Its services can be accessed through its Alison-SDK library, compatible with any browser (IExplorer 11, Edge, Firefox, Chrome, Safari, Opera, Brave).
It can be accessed using Alison-SDK. From Alison-Desktop 3.x a new REST interface is available for generation, installation and testing.
Alison-Desktop was tested on the following platforms:
Image Removed
| Image Removed
| Image Removed
|
---|
Windows 10 | MacOS 10.15 (Catalina) | Ubuntu 18.04.3 LTS |
Windows 8 | MacOS 10.14 (Mojave) | Windows 7 | MacOS 10.13 (High Sierra) | Alison SDK js
Alison SDK allows developer to integrate Alison Desktop in its pages in a easier way. Go to the Alison SDK documentation.
Alison Wizard
You can obtain current version of Alison Desktop from ACME Alison Wizard site.
For developers, go to the Alison Desktop documentation.
Features
Available KeyStore List
New KeyStores are included on any new version of Alison-Desktop.
Value | Description | Image Removed
| Image Removed
| Image Removed |
---|
WIN-ENH | Native and regular Windows CSP used to generate and store certificate for users. | ✔ | CSK | Propietary repository, linked to computer hardware to provide a more secure repository | ✔ | ✔ | ✔ |
ETOKEN | Gemalto eToken | ✔ | ✔ | MTOKEN | Century Longmai mToken | ✔ | ✔ | MACOS | Keychain respository of certificated used by OSX | ✔ | FF-NSS | Repository used by Mozilla Firefox | ✔ | ✔ | YUBIKEY | Yubico | ✔ | EPASS | Feitian ePass | ✔ | ✔ | ATHE-PIV | Athena PIV | ✔ | ✔ | PFX | Repository of certificate using a PKCS12 file | ✔ | ✔ | ✔ |
a SDK jsAlisonSDK type on on another User your title | KeyStoreInfo JSON structure,
"providerId": "Certificate provider (usually Alison-Desktop) keyStore keyStore othertext | title | Profile JSON information an keyStore Number Number .details | Details of the profileIt's used to indicate a unique KeyStore and a profile into it.
Some methods, like migration of certificate between keystores, use a KeyStoreSelector to indicate the target keystore where to move the certificate.
titleKeyStore Selector Structure | providerIdwhen the is managed by another thanDestkopCertificate Selector
This structure is used to reference a unique certificate managed by Alison-Desktop or Alison-Server.title | Certificate Selector Structure |
keyStoreIdkeyStoreId where is storedprofileNameprofileNamewherethecertificate isstoredcertificate thumbprintproviderIdcertificate provider (usually Alison-Desktop)"
} Anchor |
---|
WebCertificate | WebCertificate | WebCertificateA WebCertificate is the representation of a certificate that is stored in a keystore. It contains all the information of the certificate such as subject, issuer and thumbprint.
Code Block |
---|
language | text |
---|
title | WebCertificate Structure |
---|
|
{
"serialNumber": "The serial number of the certificate",
"serialNumberH": "The serial number in hexadecimal",
"thumbPrint": "A unique identifiernotBeforeSbefore, in a string format
YYYY-MM-DD HH:MM:SS GMT-0notAfterSNot-after value of,inastringformat YYYY-MM-DD HH:MM:SS GMT-0"daysToExpireDaysbeforeexpiration",
"notBeforeTS": "Not-Before timestamp value of the certificate",
"notAfterTS": "Not-After timestamp value of the certificate",
"isDefault": "True is the certificate is the last used
(when the certificate is included in a list of certificates)",
"status": "Certificate status (valid | revoked ) (-1 is UNDEF)" *,
"trustLevel": "TrustLevel used during its validation.
It depends on the Debbie validation policy used" *,
"validationMode": "Indicates the validation mode used by Debbie" *,
"profile": Basic information about the profile that contains this certificate,
"subject": {
"DN": "Distringuished Name of the Subject",
"parsedDN": "JSON Object that represents de DN"
},
"issuer": {
"DN": "Distringuished Name of the Issuer",
"parsedDN": "JSON Object that represents the DN"
},
"extensions": Some principal extensions defined into the certificate,
"pkcs7": "Certificate in PEM format",
"keyStoreId": "KeyStore Identifier",
"keyStoreType": "KeyStore Type"
}* This fields are completed by Debbie.
Result StatusThis structure is used to represent the status of several elements (keystore, profile, etc).
Code Block |
---|
language | text |
---|
title | Result Status Structure |
---|
|
"status": {
"resultStatus": "[ 0 | 1 | 2 ] ",
"resultList":
[
{ "code": "result code",
"detail": "result code detail"
},
...
]
} |
Field | Description |
---|
resultStatus | It's an integer value, where 0 represents that there is no error, 1 is used to alert about some special condition, which must be taken in consideration, (for example, that a cryptographic device is almost full), and 2 indicates an error on the keystore (for example, if it is locked) |
resultList | It's a list of pair key-values (code, detail), where **code** contains a warning or error code, and **detail** may contain information about the code. |
ErrorCode responses
Error code responses are returned with the following structure:
Code Block |
---|
language | text |
---|
title | ErrorCode response structure |
---|
|
{
"code": 20611,
"message": "Token is not present or is empty"
}