walterww

Thank you very much! [quote]So adding the check would probably be a good idea anyway.[/quote] Yes, I will do that!

I've got a script running that pauses our Ultimakers when they print without authorization. The new firmware seems to crash when the scripts tries to pause the printer while it is resuming from a prior pause. The API command I'm using is PUT /print_job/state with payload {"target": "pause"} and I'm calling it without checking first if the printer is already paused or has just been unpaused and not resumed printing yet. This worked flawlessly for years now, so I think this is due to a change in the last firmware update. So in order to reproduce: Start a print. Pause the print. Resume and immediately send PUT /print_job/state with payload {"target": "pause"} The print bed goes down and I think it crashes. On the display there's an ERR999 and Reboot button The Management Console says: Unhandled exception from ProcedureStep TEST_IF_NOT_PAUSED And the log file says:

@Josnoww Wow, this is really helpful! Thank you. I'm not afraid of a little SSH. @tomnagel Yes I can explain that. Short version: I didn't know that and generate new API keys after every upgrade. Yes that sounds stupid, but here's the long version: We are a Maker Space where people are allowed to use our machines on their own. So in order to keep track of who does what, and also to limit the use to active users (i.e. paying customers) who attended the respective safety course, we use a management system (fabman.io) that uses NFC readers to authenticate users and activate machines. Many machines are simply switched on and off using a relay, but for the UltimakerS I was able to code a python script that runs ON THE PRINTER, watches printer status and checks if anyone has been authenticated when a job starts. If not, the job is paused. And it also logs how much material was used by whom, which saves us a lot of trouble. I love you for this! 😄 This script is purged from the printer's filesystem every time a new firmware version is installed; but that's OK for me, I wrote an installation script that copies the script to the printers and configures them to start it automatically as well. I was not aware that the API keys are retained during a normal firmware upgrade, as my keys never leave the printers... my installation script creates a new key after every reinstall. I think @Josnoww just helped me getting rid of having to do that. (I could run the script on a server in our network instead of on the printers, but a creative user could simply turn off a printer's WiFi or network and print for free. I'm quite sure we'd figure out who it was, but that costs time and none the less we try to make our authentication system as secure as possible.)

Hi Tom, thank you for your help! We will probably downgrade to 7.1.3 and skip firmware 8.1. Unless. is there perhaps another workaround? Is there a config file or something similar I could modify in DEV mode/SSH console in order to enable an id/key pair?

Hello there, we're controlling a few Ultimakers through the local API and depend heavily on this feature. It seems the new version 8.1 doesn't show the authentication method described in the API documentation does not work anymore: [qutote]To get a valid username/password combination, the following process can/should be followed. 1) POST /auth/request with 'application' and 'user' as parameters. The application name and user name will be shown to the user on the printer. The reply body will contain a json reply with an 'id' and 'key' part.[/quote] The request is not shown on the printer's display anymore (and the id/key pair can therefore not be allowed). Without this some API calls don't work.