i did grant user permission to server. but i still got error when changing the api key.
but when i GetSecret, i am able to get the api key from the deadlinecommand.
i did tried to use additional Ayon Server
http://192.168.1.59:5000@APIKEY
with this, i am able to submit the and render the task. but i during the publish task , it came out with the same error " invalid ayon_api_key "
I wonder if this is the same as
Yea I havent got around to fixing this issue by the way, I just add those ENV vars on the deadline job to make it work for now. So if you guys find a solve I’d love to know!
Please do report the issue with Deadline support - it’s a native feature on their end to allow storing passwords in plug-in settings the way we do. So it may be worth following up with Deadline to get an understanding of why it’s disallowing such a field for your setup.
At this point it seems like a Deadline issue at it’s core - where it’s not allowing you to save.
yep its the same. tried all the fix in the post even the hardcode one.
did you manually input the api in each task ? or is there a workaround ?
stick them in here on each task.
You could make a pre/post-job script to add the env vars to them too i guess: Job Scripts — Deadline 10.1.23.6 documentation
If you really don’t care the easiest hack I’ve seen others do is…
Go to the AYON Deadline Plug-in: Ayon/Ayon.param and open it in notepad.
Find:
[AyonApiKey]
Type=password
Change it to:
[AyonApiKey]
Type=string
You can now configure this key in plain-text without Deadline bitching about any of its security features. If you’re fine with just throwing all the stuff into the env of jobs anyways I guess you’re just as fine with having these plug-in settings for an API key settable in plain text.
It may even work (although I haven’t tried)… to set it to string, set the value, and then change it back to password. I assume it won’t work, but you never know. 
And of course, sharing the Deadline docs for Secrets Management.
thanks! this is much easier than creating custom event!