Daniel Turkington (who is the POC for our development questions) addressed a few of the concerns we were having about the project. We were wondering if we needed a certificate in order to install onto the device but Daniel said that the fls file contains a developer certificate which contains all the MAC addresses of development machines. Therefore he believes that we shouldn't have any problems with building the application in that respect.
Daniel also showed us how to access the printer log by
1. Type "<printer ip address>/se" in your browser
2. Click "Embedded Solutions"
3. Click "Log File"
We still need to have the OAuth issue addressed about needing to log in with a browser on the device despite not having a browser. I did just now find this document https://developers.google.com/accounts/docs/OAuth2ForDevices.
The document states that for a printer device we will have to display a url for the user to navigate to on a device with a browser and they will have to put in the user code that we provide. Once they have done this, our application will have to poll the endpoint to see when the user has allowed the app access to their calendar. We will need to store the the access token as well as the refresh token. The access token expires after a given amount of time so we will need to check the validity of the access token and use the refresh token if the access token has expired.