@sgoodman While this is a good point and I like the idea of a cleanup it’s not as easy as removing those options I am afraid. There is quite some code logic in the background that I would argue needs a cleanup together with this as well.
Not sure if we should consider removing it all in a rush now. Sure we can just remove the UI part of it quickly. But all the rest would then stay in the code for way longer I suppose.
Was an encrypted string “semi-supported” for some time after the commit? Did a recent update nullify that?
From what I understand about the code it seems to try both ways - un-encrypted and encrypted - line 40ff. This has not changed since Feb 1, 2018. Neither hast the fog-client code changed since Apr 10, 2018 (0.11.16 released together with 1.5.1). Is it possible you changed your AD logon credentials in the last weeks and somehow hit some kind of special case with character encoding that we were not aware of? Just guessing here.
I use “technicians” to help me deploy (students) and they are not normally given this credential as it could create a security concern.
We are working on this - see github issue. Tom added it to the working-1.6 branch already and I will adapt this to dev-branch today.