The FDO All-In-One demo is designed to run multiple FDO services like Manufacturer, Rendezvous and Owner Service in a single docker instance. The purpose of this demo is to fast-track demonstration of FDO protocol using different client implementations.
NOTE: The All-In-One demo is provided to demonstrate out-of-the-box operation of FDO components. Appropriate security measures with respect to key-store management and credential management should be considered while performing production deployment of any FDO component.
The following are the system requirements for the All-in-One demo.
- Host Operating System: Ubuntu (20.04, 22.04) / RHEL (8.4, 8.6) / Debian 11.4
- Java* Development Kit 17
- Apache Maven* 3.5.4 (Optional) software for building the demo from source
- Java IDE (Optional) for convenience in modifying the source code
- Docker 20.10.10+ / Podman engine 3.4.2+(For RHEL)
- Docker compose 1.29.2 / Podman-compose 1.0.3(For RHEL)
- Haveged
Appropriate proxy configuration should be updated in _JAVA_OPTIONS
environment variable. (Mandatory, if you are working behind a proxy.)
Update the proxy information in _JAVA_OPTIONS as _JAVA_OPTIONS=-Dhttp.proxyHost=http_proxy_host -Dhttp.proxyPort=http_proxy_port -Dhttps.proxyHost=https_proxy_host -Dhttps.proxyPort=https_proxy_port
.
Use the following commands to build FIDO Device Onboard (FDO) All-In-One Component sample source.
For the instructions in this document, <fdo-pri-src>
refers to the path of the FDO PRI folder 'pri-fidoiot'.
$ cd <fdo-pri-src>/component-samples/aio/
$ mvn clean install
This will copy the required executables and libraries into <fdo-pri-src>/component-samples/demo/aio/.
All the runtime configurations for the services are specified in four files: service.env
, hibernate.cfg.xml
, service.yml
& WEB-INF/web.xml
and are present in <fdo-pri-src>/component-samples/demo/aio/
.
service.env
: consists of all the credentials used by the All-in-one demo service. These credential configurations are to be generated freshly for each deployment.
hibernate.cfg.xml
: consists of all the database configurations used by the All-in-one demo service. This file can be configured to pick various database tables and properties.
service.yml
file is structured into multiple sections:
-
hibernate-properties:
- This section contains *Hibernate related runtime properties including the DB URL, dialect and others. -
system-properties:
- This section contains the runtime environment variables. -
http-server:
- This section contains the *Tomcat server related properties including ports, schemes, keystore information and api authentication setup. -
manufacturer:
- This section contains the configuration related to manufacturer keystore path, type and credentials. -
owner:
- This section contains the configuration related to Owner keystore path, type and credentials. -
secrets:
- This section contains path to the service credentials. -
cwt:
- This section contains the configuration related to CBOR web token (cwt) keystore path, type and credentials. -
workers:
The section contains the configuration to select desired functionality for the services. The deployer can pick and choose the functionality during runtime.
WEB-INF/web.xml
: consist of the all configurations related to REST endpoints served. The deployer can pick and choose the served endpoints during runtime.
The All-In-One demo can be executed as a standalone service as well as a docker service. At the
end of initialization of all services, you will see following statement on the console. Generate the required credentials keypair and certificates using the 'keys_gen.sh' script present in <fdo-pri-src>/component-samples/demo/scripts/
[INFO] Started All-in-one demo Service.
Follow the below steps to start All-In-One demo.
Open a terminal, change directory to <fdo-pri-src>/component-samples/demo/aio/
and execute following command.
java -jar aio.jar
Make sure to export the credential environment variables set in service.env
file.
Open a terminal, change directory to <fdo-pri-src>/component-samples/demo/aio/
and execute following command.
docker-compose up --build
In case you need super user access, prefix 'sudo -E' to above command.
NOTE : To support OnDie ECDSA Device attestation, copy the required certificates and crls to <fdo-pri-src>/component-samples/aio/ondiecache
folder.
NOTE: These REST APIs use Digest authentication. api_user
and api_password
properties specify the credentials to be used while making the REST calls. The value for api_user
is present in service.yml
file and value for api_password
is present in service.env
file.
NOTE: Follow the steps to port DIGEST auth calls with mTLS enabled cURL requests. READ MORE
Operation | Description | Path/Query Parameters | Content Type | Request Body | Response Body | Sample cURL call |
---|---|---|---|---|---|---|
GET /api/v1/deviceinfo/{seconds} | Serves the serial no. and GUID of the devices that completed DI in the last n seconds |
n seconds |
Serial No, GUID and Timestamp of device that completed DI | curl -D - --digest -u ${api_user}:${api_password} --location --request GET 'http://host.docker.internal:8080/api/v1/deviceinfo/30' | ||
GET /api/v1/to0/{guid} | initiate TO0 from Owner | GUID of the device to initiate TO0 | text/plain | curl -D - --digest -u ${api_user}:${api_password} --location --request GET "http://host.docker.internal:8080/api/v1/to0/${device_guid}" | ||
POST /api/v1/aio/rvinfo?ip=ip-address&rvprot=(http or https) | allows to update rvInfo with ipaddress and rv protocol | ip => ip-address of machine running aio & rvprot => supported rvProtocol | text/plain | curl -D - --digest -u ${api_user}: --location --request POST 'http://host.docker.internal:8080/api/v1/aio/rvinfo?ip=127.0.0.1&rvprot=http' --header 'Content-Type: text/plain' | ||
GET /api/v1/logs | Serves the log from the AIO service | AIO logs | curl -D - --digest -u ${api_user}: --location --request GET 'http://host.docker.internal:8080/api/v1/logs' | |||
DELETE /api/v1/logs | Deletes the log from the AIO service | curl -D - --digest -u ${api_user}: --location --request DELETE 'http://host.docker.internal:8080/api/v1/logs' | ||||
GET /health | Returns the health status | Current version | curl -D - --digest -u ${api_user}: --location --request GET 'http://host.docker.internal:8080/health' | |||
GET /api/v1/owner/state/{guid} | Returns the TO status the associated GUID | GUID of the device | Returns TO2 completed status & TO0 expiry (timestamps) | curl -D - --digest -u ${api_user}: --location --request GET 'http://host.docker.internal:8080/api/v1/owner/state/{guid}' |
NOTE: These REST APIs use Digest authentication. api_user
and api_password
properties specify the credentials to be used while making the REST calls. The value for api_user
is present in service.yml
file and value for api_password
is present in service.env
file.
Operation | Description | Path/Query Parameters | Content Type | Request Body | Response Body | Sample cURL call |
---|---|---|---|---|---|---|
POST /api/v1/mfg/vouchers/<serial_no> | Gets extended Ownership Voucher with the serial number. | Path - Device Serial Number | Owner Certificate | Extended Voucher | curl -D - --digest -u ${api_user}: --location --request POST "http://host.docker.internal:8080/api/v1/mfg/vouchers/${serial_no}" --header 'Content-Type: text/plain' --data-raw "$owner_certificate" -o ${serial_no}_voucher.txt | |
GET /api/v1/certificate?filename=fileName | Returns the certificate file based on filename | Query - filename | Keystore file in binary format | curl -D - --digest -u ${api_user}: --location --request GET 'http://host.docker.internal:8080/api/v1/certificate?filename=ssl.p12' | ||
POST /api/v1/certificate?filename=fileName | Adds the certificate file to DB based on filename | Query - filename | text/plain | PKCS12 Certificate file in Binary format | curl -D - --digest -u ${api_user}: --location --request POST 'http://host.docker.internal:8080/api/v1/certificate?filename=ssl.p12' --header 'Content-Type: text/plain' --data-binary '@< path to ssl.p12 >' | |
DELETE /api/v1/certificate?filename=fileName | Delete the certificate file to DB based on filename | Query - filename | curl -D - --digest -u ${api_user}: --location --request DELETE 'http://host.docker.internal:8080/api/v1/certificate?filename=ssl.p12' --header 'Content-Type: text/plain' | |||
POST /api/v1/rvinfo/ | Updates RV Info in RV_DATA table |
text/plain | RV Info | curl -D - --digest -u ${api_user}: --location --request POST 'http://host.docker.internal:8080/api/v1/rvinfo' --header 'Content-Type: text/plain' --data-raw '[[[5,"host.docker.internal"],[3,8080],[12,1],[2,"127.0.0.1"],[4,8443]]]' | ||
GET /api/v1/deviceinfo/{seconds} | Serves the serial no. and GUID of the devices that completed DI in the last n seconds |
Path - n seconds |
JSON array of Serial No, GUID ,DI Timestamp and Attestion type. | curl -D - --digest -u apiUser: --location --request GET 'http://host.docker.internal:8080/api/v1/deviceinfo/30' --header 'Content-Type: text/plain' | ||
GET /api/v1/logs | Serves the log from the manufacturer service | Manufacturer logs | curl -D - --digest -u ${api_user}: --location --request GET 'http://host.docker.internal:8080/api/v1/logs' --header 'Content-Type: text/plain' | |||
DELETE /api/v1/logs | Deletes the log from the manufacturer service | curl -D - --digest -u ${api_user}: --location --request DELETE 'http://host.docker.internal:8080/api/v1/logs' --header 'Content-Type: text/plain' | ||||
POST /api/v1/certificate/validity?days=no_of_days | Updates certificate validity in CERTIFICATE_VALIDITY table |
Query - days | text/plain | curl -D - --digest -u ${api_user}: --location --request POST 'http://host.docker.internal:8080/api/v1/certificate/validity?days=10' --header 'Content-Type: text/plain' | ||
GET /api/v1/certificate/validity | Collects certificate validity days from CERTIFICATE_VALIDITY table |
Number of Days | curl -D - --digest -u ${api_user}: --location --request GET 'http://host.docker.internal:8080/api/v1/certificate/validity' | |||
GET /health | Returns the health status | Current version | curl -D - --digest -u ${api_user}: --location --request GET 'http://host.docker.internal:8080/health' |
Operation | Description | Path/Query Parameters | Content Type | Request Body | Response Body | Sample cURL call |
---|---|---|---|---|---|---|
GET /api/v1/certificate?filename=fileName | Returns the certificate file based on filename | Query - filename | Certificate file in PKCS12 format | curl -D - --digest -u ${api_user}: --location --request GET 'http://host.docker.internal:8080/api/v1/certificate?filename=ssl.p12' | ||
POST /api/v1/certificate?filename=fileName | Adds the certificate file to DB based on filename | Query - filename | text/plain | PKCS12 Certificate file in Binary format | curl -D - --digest -u ${api_user}: --location --request POST 'http://host.docker.internal:8080/api/v1/certificate?filename=ssl.p12' --data-binary '@< path to ssl.p12 >' | |
DELETE /api/v1/certificate?filename=fileName | Delete the certificate file to DB based on filename | Query - filename | curl -D - --digest -u ${api_user}: --location --request DELETE 'http://host.docker.internal:8080/api/v1/certificate?filename=ssl.p12' --header 'Content-Type: text/plain' | |||
GET /api/v1/logs | Serves the log from the RV service | RV logs | curl -D - --digest -u ${api_user}: --location --request GET 'http://host.docker.internal:8080/api/v1/logs' | |||
DELETE /api/v1/logs | Deletes the log from the RV service | curl -D - --digest -u ${api_user}: --location --request DELETE 'http://host.docker.internal:8080/api/v1/logs' | ||||
POST /api/v1/certificate/validity?days=no_of_days | Updates certificate validity in CERTIFICATE_VALIDITY table |
text/plain | curl -D - --digest -u ${api_user}: --location --request POST 'http://host.docker.internal:8080/api/v1/certificate/validity?days=10' | |||
GET /api/v1/certificate/validity | Collects certificate validity days from CERTIFICATE_VALIDITY table |
Number of Days | curl -D - --digest -u ${api_user}: --location --request GET 'http://host.docker.internal:8080/api/v1/certificate/validity' | |||
GET /health | Returns the health status | Current version | curl -D - --digest -u ${api_user}: --location --request GET 'http://host.docker.internal:8080/health' | |||
POST /api/v1/rv/allow | Adds public key to allowed list of Owners in RV | text/plain | certificate in pem format | curl -D - --digest -u ${api_user}: --location --request POST 'http://host.docker.internal:8080/api/v1/rv/allow` --data-raw "$owner_certificate" | ||
DELETE /api/v1/rv/allow | delete public key to allowed list of Owners in RV | text/plain | certificate in pem format | curl -D - --digest -u ${api_user}: --location --request DELETE 'http://host.docker.internal:8080/api/v1/rv/allow` --data-raw "$owner_certificate" | ||
POST /api/v1/rv/deny | Adds public key to denied list of Owners in RV | text/plain | certificate in pem format | curl -D - --digest -u ${api_user}: --location --request POST 'http://host.docker.internal:8080/api/v1/rv/deny` --data-raw "$owner_certificate" |
Operation | Description | Path/Query Parameters | Content Type | Request Body | Response Body | Sample cURL call |
---|---|---|---|---|---|---|
POST /api/v1/owner/redirect | Updates TO2 RVBlob in ONBOARDING_CONFIG table. |
text/plain | RVTO2Addr in diagnostic form | curl -D - --digest -u ${api_user}: --location --request POST 'http://host.docker.internal:8080/api/v1/owner/redirect' --header 'Content-Type: text/plain' --data-raw '[["127.0.0.1","host.docker.internal",8080,3]]' | ||
GET /api/v1/to0/{guid} | initiate TO0 from Owner | GUID of the device to initiate TO0 | curl -D - --digest -u ${api_user}: --location --request GET "http://host.docker.internal:8080/api/v1/to0/${device_guid}" --header 'Content-Type: text/plain' | |||
POST /api/v1/owner/svi | Uploads SVI instructions to SYSTEM_PACKAGE table. |
text/plain | SVI Instruction | curl -D - --digest -u ${api_user}: --location --request POST 'http://host.docker.internal:8080/api/v1/owner/svi' --header 'Content-Type: text/plain' --data-raw '[{"filedesc" : "setup.sh","resource" : "URL"}, {"exec" : ["bash","setup.sh"] }]' | ||
GET /api/v1/owner/vouchers | Returns a list of all Ownership Voucher GUIDs. | line separated list of GUIDs | curl -D - --digest -u ${api_user}: --location --request GET "http://host.docker.internal:8080/api/v1/owner/vouchers" --header 'Content-Type: text/plain' | |||
GET /api/v1/owner/vouchers/<device_guid> | Returns the Ownership Voucher for the specified GUID. | Path - id: Device GUID | Ownership Voucher | curl -D - --digest -u ${api_user}: --location --request GET "http://host.docker.internal:8080/api/v1/owner/vouchers/${device_guid}" --header 'Content-Type: text/plain' | ||
POST /api/v1/owner/vouchers/ | Insert Ownership Voucher against the specified GUID in ONBOARDING_VOUCHER table. |
text/plain | Content of Ownership Voucher in PEM Format | Guid of the device | curl -D - --digest -u ${api_user}: --location --request POST "http://host.docker.internal:8080/api/v1/owner/vouchers" --header 'Content-Type: text/plain' --data-raw '${voucher}' | |
GET /api/v1/owner/vouchers/ | Returns the Ownership Voucher for the specified serial number. | Path - id: Device SerialNo | Ownership Voucher | curl -D - --digest -u ${api_user}: --location --request GET "http://host.docker.internal:8080/api/v1/owner/vouchers/${device_serialno}" --header 'Content-Type: text/plain' | ||
POST /api/v1/owner/vouchers/ | Insert Ownership Voucher against the specified serialnumber in ONBOARDING_VOUCHER table. The serialno to guid mapping will be preserved in 'VOUCHER_ALIAS' table |
text/plain | Content of Ownership Voucher in PEM Format | Guid of the device | curl -D - --digest -u ${api_user}: --location --request POST "http://host.docker.internal:8080/api/v1/owner/vouchers/${device_serialno}" --header 'Content-Type: text/plain' --data-raw '${voucher}' | |
GET /api/v1/logs | Serves the log from the owner service | owner logs | curl -D - --digest -u ${api_user}: --location --request GET 'http://host.docker.internal:8080/api/v1/logs' | |||
DELETE /api/v1/logs | Deletes the log from the owner service | curl -D - --digest -u ${api_user}: --location --request DELETE 'http://host.docker.internal:8080/api/v1/logs' | ||||
GET /health | Returns the health status | Current version | curl -D - --digest -u ${api_user}: --location --request GET 'http://host.docker.internal:8080/health' | |||
GET /api/v1/ondie | Serves the stored certs & crls files | Ondie certs & crl files | curl -D - --digest -u ${api_user}: --location --request GET 'http://host.docker.internal:8080/api/v1/ondie' | |||
POST /api/v1/ondie | To insert onDie certs and crls zip file to DB | text/plain | Path to ondie cert file | curl -D - --digest -u ${api_user}:${api_passwd} --location --request POST "http://${ip}:{port}/api/v1/ondie" --header 'Content-Type: text/plain' --data-raw "${cert-file}" | ||
GET /api/v1/certificate?filename=fileName | Returns the certificate file based on filename | Query - filename | Certificate file in PKCS12 format | curl -D - --digest -u ${api_user}: --location --request GET 'http://host.docker.internal:8080/api/v1/certificate?filename=ssl.p12' | ||
GET /api/v1/certificate?alias={alias} | Returns the owner certificate of the given alias type | Query - alias | Certificate PEM format | curl -D - --digest -u ${api_user}: --location --request GET 'http://host.docker.internal:8080/api/v1/certificate?alias=SECP256R1' --header 'Content-Type: text/plain' | ||
GET /api/v1/certificate?uuid=uuid | Returns the owner alias type for the given voucher | Query - uuid | UUID's attestation type | curl -D - --digest -u ${api_user}: --location --request GET 'http://host.docker.internal:8080/api/v1/certificate?uuid=cc60f0aa-56d0-492e-8c8d-9a1fe55cb60 --header 'Content-Type: text/plain' | ||
POST /api/v1/certificate?filename=fileName | Adds the certificate file to DB based on filename | Query - filename | text/plain | PKCS12 Certificate file in Binary format | curl -D - --digest -u ${api_user}: --location --request POST 'http://host.docker.internal:8080/api/v1/certificate?filename=ssl.p12' --header 'Content-Type: text/plain' --data-binary '@< path to ssl.p12 >' | |
DELETE /api/v1/certificate?filename=fileName | Delete the certificate file to DB based on filename | Query - filename | curl -D - --digest -u ${api_user}: --location --request DELETE 'http://host.docker.internal:8080/api/v1/certificate?filename=ssl.p12' --header 'Content-Type: text/plain' | |||
POST /api/v1/certificate/validity?days=no_of_days | Updates certificate validity in CERTIFICATE_VALIDITY table |
text/plain | curl -D - --digest -u ${api_user}: --location --request POST 'http://host.docker.internal:8080/api/v1/certificate/validity?days=10' --header 'Content-Type: text/plain' | |||
GET /api/v1/certificate/validity | Collects certificate validity days from CERTIFICATE_VALIDITY table |
Number of Days | curl -D - --digest -u ${api_user}: --location --request GET 'http://host.docker.internal:8080/api/v1/certificate/validity' | |||
GET /api/v1/owner/messagesize | Collects the max message size from ONBOARDING_CONFIG table |
MAX_MESSAGE_SIZE | curl -D - --digest -u ${api_user}: --location --request GET 'http://host.docker.internal:8080/api/v1/owner/messagesize' --header 'Content-Type: text/plain' | |||
POST /api/v1/owner/messagesize | Updates the max message size in ONBOARDING_CONFIG table |
text/plain | MAX_MESSAGE_SIZE | curl -D - --digest -u ${api_user}: --location --request POST 'http://host.docker.internal:8080/api/v1/owner/messagesize' --header 'Content-Type: text/plain' --data-raw '10000' | ||
GET /api/v1/owner/svisize | Collects the owner svi size from ONBOARDING_CONFIG table |
SVI_MESSAGE_SIZE | curl -D - --digest -u ${api_user}: --location --request GET 'http://host.docker.internal:8080/api/v1/owner/svisize' --header 'Content-Type: text/plain' | |||
POST /api/v1/owner/svisize | Updates the owner svi size in ONBOARDING_CONFIG table |
text/plain | SVI_MESSAGE_SIZE | curl -D - --digest -u ${api_user}: --location --request POST 'http://host.docker.internal:8080/api/v1/owner/svisize' --header 'Content-Type: text/plain' --data-raw '10000' | ||
GET /api/v1/owner/resource?filename=fileName | Returns the file based on filename from SYSTEM_RESOURCE table |
Query - filename | file content | curl -D - --digest -u ${api_user}: --location --request GET 'http://host.docker.internal:8080/api/v1/owner/resource?filename=fileName' --header 'Content-Type: text/plain' | ||
POST /api/v1/owner/resource?filename=fileName | Adds the file to DB based on filename from SYSTEM_RESOURCE table |
Query - filename | text/plain | file in Binary format | curl -D - --digest -u ${api_user}: --location --request POST 'http://host.docker.internal:8080/api/v1/owner/resource?filename=fileName' --header 'Content-Type: text/plain' --data-binary '@< path to file >' | |
DELETE /api/v1/owner/resource?filename=fileName | Delete the file from DB based on filename from SYSTEM_RESOURCE table |
Query - filename | curl -D - --digest -u ${api_user}: --location --request DELETE 'http://host.docker.internal:8080/api/v1/owner/resource?filename=fileName' --header 'Content-Type: text/plain' | |||
POST /api/v1/resell/{guid} | Gets extended resell Ownership Voucher with the guid. | Path - guid of the device to resell | Owner Certificate | The Ownership voucher in PEM format | curl -D - --digest -u ${api_user}: --location --request POST "http://host.docker.internal:8080/api/v1/resell/${guid}" --header 'Content-Type: text/plain' --data-raw "$owner_certificate" -o ${serial_no}_voucher.txt | |
GET /api/v1/owner/state/{guid} | Returns the TO status the associated GUID | GUID of the device | Returns TO2 completed status & TO0 expiry (timestamps) | curl -D - --digest -u ${api_user}: --location --request GET 'http://host.docker.internal:8080/api/v1/owner/state/{guid}' |
Operation | Description | Path/Query Parameters | Content Type | Request Body | Response Body | Sample cURL call |
---|---|---|---|---|---|---|
POST /api/v1/resell/{guid} | Gets extended resell Ownership Voucher with the guid. | Path - guid of the device to resell | Owner Certificate | The Ownership voucher in PEM format | curl -D - --digest -u ${api_user}: --location --request POST "http://host.docker.internal:8080/api/v1/resell/${guid}" --header 'Content-Type: text/plain' --data-raw "$owner_certificate" -o ${serial_no}_voucher.txt | |
GET /api/v1/owner/vouchers | Returns a list of all Ownership Voucher GUIDs. | line separated list of GUIDs | curl -D - --digest -u ${api_user}: --location --request GET "http://host.docker.internal:8080/api/v1/owner/vouchers" --header 'Content-Type: text/plain' | |||
GET /api/v1/owner/vouchers/<device_guid> | Returns the Ownership Voucher for the specified GUID. | Query - id: Device GUID | Ownership Voucher | curl -D - --digest -u ${api_user}: --location --request GET "http://host.docker.internal:8080/api/v1/owner/vouchers/${device_guid}" --header 'Content-Type: text/plain' | ||
POST /api/v1/owner/vouchers/ | Insert Ownership Voucher against the specified GUID in ONBOARDING_VOUCHER table. |
text/plain | Content of Ownership Voucher in PEM Format | curl -D - --digest -u ${api_user}: --location --request POST "http://host.docker.internal:8080/api/v1/owner/vouchers" --header 'Content-Type: text/plain' --data-binary '${voucher}' |
Following is the list of REST response error codes and it's possible causes :
Error Code | Possible Causes |
---|---|
401 Unauthorized |
When an invalid Authentication header is present with the REST Request. Make sure to use the correct REST credentials. |
404 Not Found |
When an invalid REST request is sent to AIO. Make sure to use the correct REST API endpoint. |
405 Method Not Allowed |
When an unsupported REST method is requested. Currently, AIO supports GET, POST and DELETE only. |
406 Not Acceptable |
When an invalid filename is passed through the REST endpoints. |
500 Internal Server Error |
Due to internal error, AIO unable to fetch/copy/delete the requested file. |
Alias values that can be used for GET /api/v1/certificate?alias={alias}
Alias |
---|
SECP384R1 |
SECP256R1 |
RSAPKCS3072 |
RSAPKCS2048 |
RSA2048RESTR |
Service info is a single json document store in the database. To define different service info instructions for a given set of device info properties you can use filters.
Every service info following a filter will only be returned if the filter matches. If no filter is specified or if the filter is empty then the service info following the empty filter will apply to all devices.
The following filter will only return service info instructions if the device info reports the device is a "FDO-Pri-Device"
[ {"filedesc" : "setup.sh","resource" : "payload.bin", "filter": {"device" : "FDO-Pri-Device"}}, {"exec" : ["bash","setup.sh"] } ]
The following filter will only return service info instructions if the device info reports the os is linux
[ {"filedesc" : "setup.sh","resource" : "payload.bin", "filter": {"devmod:os" : "linux"}}, {"exec" : ["bash","setup.sh"], "filter": {"devmod:os" : "linux"}} ]
The following filter will only return service info instructions if the device info reports the os is linux and verion is 20.04
[ {"filedesc" : "setup.sh","resource" : "payload.bin", "filter": {"devmod:os" : "linux", "devmod:version" : "Ubuntu 20.04 LTS"}}, {"exec" : ["bash","setup.sh"] } ]
Increase the heap size appropriately in case you encounter heap size issues.
By default, the AIO uses HTTP for all communications on port 8080. In addition to that, the AIO can be configured to handle HTTPS requests from the device.
AIO can generate its own certificate and if you want to override the default certificate, follow these steps:
-
Generate the Keystore/Certificate for the AIO. REFER
- Ensure that the web certificate is issued to the resolvable domain of the AIO server.
-
Copy the generated Keystore/Certificate to
.app-data
folder and update credentials inservice.yml
file. -
Update the SSL keystore password & subject_names in
service.yml
file.
Workers are java classes the implement various behavioral aspects of an FDO service. Workers are defined in the workers section of the service.yml.
worker | Description |
---|---|
org.fidoalliance.fdo.protocol.HttpOwnerSchemeSupplier | Tells the owner to use HTTP instead of HTTPS for TO0 protocol |
org.fidoalliance.fdo.protocol.RemoteDatabaseServer | Provides access to an external database |
org.fidoalliance.fdo.protocol.SelfSignedHttpClientSupplier | Tells HTTPS Clients to trust self-signed certificates |
org.fidoalliance.fdo.protocol.StandardCertSignatureFunction | Provides CSR signing for Device Initialization protocol. |
org.fidoalliance.fdo.protocol.StandardCryptoService | Provides cryptographic services (e.g. sign, verify, random number generation etc) |
org.fidoalliance.fdo.protocol.StandardCwtKeySupplier | Provides Cbor Web token signing key for RV server (TO0 and TO1 auth tokens) |
org.fidoalliance.fdo.protocol.StandardDatabaseServer | Provides an embedded H2 Database server |
org.fidoalliance.fdo.protocol.StandardHttpServer | Provides an embedded Tomcat HTTP server for handling messages |
org.fidoalliance.fdo.protocol.StandardLogProvider | Providers logging services for other workers (must be first defined worker) |
org.fidoalliance.fdo.protocol.StandardManufacturerKeySupplier | Provides manufacturing signing keys |
org.fidoalliance.fdo.protocol.StandardMessageDispatcher | Provides message processing for all FDO protocols |
org.fidoalliance.fdo.protocol.StandardOwnerKeySupplier | Provides owner signing keys |
org.fidoalliance.fdo.protocol.StandardOwnerSchemeSupplier | Tells the owner to use HTTPS for TO0 protocol |
org.fidoalliance.fdo.protocol.StandardReplacementKeySupplier | Provides Owner2 keys for for credential replacement during TO2 |
org.fidoalliance.fdo.protocol.UntrustedRendezvousAcceptFunction | Tells the RV server to allow TO0 with untrusted ownership keys |
org.fidoalliance.fdo.FileKeyStoreInputStream | Loads PRI Service keys from disk |
org.fidoalliance.fdo.FileKeyStoreOutputStream | Save PRI Service keys to disk |
org.fidoalliance.fdo.protocol.db.AutoInjectVoucherStorageFunction | Automatically extends the voucher to the AIO owner and performs To0 protocol |
org.fidoalliance.fdo.protocol.db.BasicServiceInfoClientSupplier | Uses BASIC auth with api_user api_password from service.env for serivceinfo urls (NOT Recommended) |
org.fidoalliance.fdo.protocol.db.StandardServiceInfoClientSupplier | Uses standard auth for serviceinfo urls |
org.fidoalliance.fdo.protocol.db.ConformanceOwnerModule | Provides the implementation of Fido Conformance Module for Interop |
org.fidoalliance.fdo.protocol.db.FdoSysOwnerModule | Provides the implementation of the FdoSys Module |
org.fidoalliance.fdo.protocol.db.OnDieCertificateManager | Provides Root certificate chains for Intel OnDie hardware ECDSA keys |
org.fidoalliance.fdo.protocol.db.ReuseVoucherReplacementFunction | Tells the owner to reuse the device credentials instead of replacing them during TO2 |
org.fidoalliance.fdo.protocol.db.StandardAcceptOwnerFunction | Accepts TO0 wait seconds and updates the owner database with the expiry time |
org.fidoalliance.fdo.protocol.db.StandardExtraInfoSupplier | Provides null as owner extra data in ownership voucher entries |
org.fidoalliance.fdo.protocol.db.StandardKeyStoreInputStream | Provides Keystore loading from a database table |
org.fidoalliance.fdo.protocol.db.StandardKeyStoreOutputStream | Provides Keystore storage to a database table |
org.fidoalliance.fdo.protocol.db.StandardOwnerInfoSizeSupplier | Provides the size of the service info buffer owner is willing to accept |
org.fidoalliance.fdo.protocol.db.StandardRvBlobQueryFunction | Provides TO1 redirect blobs from the RV server database |
org.fidoalliance.fdo.protocol.db.StandardRvBlobStorageFunction | Stores TO1 redirect blobs in the RV database |
org.fidoalliance.fdo.protocol.db.StandardRendezvousInfoSupplier | Provides Rendezvous instructions for ownership voucher creation |
org.fidoalliance.fdo.protocol.db.StandardRendezvousWaitSecondsSupplier | Gets the Wait Seconds amount the rv server is willing to accept |
org.fidoalliance.fdo.protocol.db.StandardReplacementVoucherStorageFunction | Stores the replacement ownership voucher at the end to TO2 |
org.fidoalliance.fdo.protocol.db.StandardServerSessionManager | Provides session storage and management for service side protocols |
org.fidoalliance.fdo.protocol.db.StandardSessionCleaner | Removes incomplete session from the database after a couple of hours |
org.fidoalliance.fdo.protocol.db.StandardValidityDaysSupplier | Provides the validity days for certificate generation |
org.fidoalliance.fdo.protocol.db.StandardVoucherQueryFunction | Provides ownership vouchers from the owner database |
org.fidoalliance.fdo.protocol.db.StandardVoucherReplacementFunction | Tells the owner to replace the device credentials during TO2 |
org.fidoalliance.fdo.protocol.db.StandardVoucherStorageFunction | Stores voucher in the database without performing To0 protocol |
org.fidoalliance.fdo.protocol.db.To0Scheduler | Performs To0 for vouchers that have expired wait seconds at regular intervals |
org.fidoalliance.fdo.protocol.db.TrustedRendezvousAcceptFunction | Tells the RV server to allow TO0 with only ownership keys that are trusted in the allow list |
org.fidoalliance.fdo.sample.ConformanceDeviceModule | The PRI Device implementation of the FIDO conformance module |
org.fidoalliance.fdo.sample.DeviceValidityDays | Sets the device certificate validity days in the CSR |
org.fidoalliance.fdo.sample.FileCredentialConsumer | Stores PRI Device credentials |
org.fidoalliance.fdo.sample.FdoSysDeviceModule | The PRI Device implementation of the Fdo_Sys Module |
org.fidoalliance.fdo.sample.FileCredentialSupplier | Loads PRI Device credentials |
org.fidoalliance.fdo.sample.FileKeyStoreInputStream | Loads PRI Device keys from disk |
org.fidoalliance.fdo.sample.FileKeyStoreOutputStream | Save PRI Device keys to disk |
org.fidoalliance.fdo.sample.StandardCredReuseFunction | Allows the PRI device to reuse credentials |
org.fidoalliance.fdo.sample.StandardDeviceKeySupplier | Provides the PRI Device Signing keys |
org.fidoalliance.fdo.sample.StandardDeviceModule | Providers the implementation of the DevMod module |
org.fidoalliance.fdo.sample.StandardHmacFunction | Generate HMAC for a voucher header using device key |
org.fidoalliance.fdo.sample.StandardMaxServiceInfoSupplier | Provides the size of the service info buffer during TO2 |
org.fidoalliance.fdo.sample.UnsupportedCredReuseFunction | Prevents the PRI device from allowing cred reuse |