Settings and activity
42 results found
-
166 votes
Matt Hardwick
supported this idea
·
-
164 votesMatt Hardwick
supported this idea
·
-
38 votesMatt Hardwick
supported this idea
·
-
18 votesMatt Hardwick
supported this idea
·
-
23 votesMatt Hardwick
supported this idea
·
-
1,256 votesMatt Hardwick
supported this idea
·
-
14 votesMatt Hardwick
supported this idea
·
-
16 votesMatt Hardwick
supported this idea
·
-
5 votesMatt Hardwick
supported this idea
·
-
55 votesMatt Hardwick
supported this idea
·
-
40 votesMatt Hardwick
supported this idea
·
-
70 votesMatt Hardwick
supported this idea
·
-
33 votes
An error occurred while saving the comment Matt Hardwick
supported this idea
·
-
34 votesMatt Hardwick
supported this idea
·
-
124 votes
Hi,
Great news! Your idea has been approved and is planned for implementation.
We appreciate your contribution and will keep you informed about the progress and expected release date, as well as here in the portal.
[For major features only–] You can also follow this in our Pubic Roadmap.
Best regards,
The Atera Team
An error occurred while saving the comment Matt Hardwick
commented
*We need the option to create per app/per customer API keys.*
There are talks here of having separate read/write API keys but it needs to go one further. We need the option to create multiple keys and define the scope, limiting the features available and/or per customer. Currently keys are transferred in the to customer devices when used in a script, and thus pose a security risk.
An error occurred while saving the comment Matt Hardwick
commented
Huge security risk to only have a singly read/write API key - I see there are suggestions for separate read/write one but realistically we should be generating keys per app and have the option to limit the scope to specific features or customers.
The API key gets transferred in the clear on PowerShell scripts to a customer device - so there really needs to be some improvements in this area.
Matt Hardwick
supported this idea
·
-
89 votes
An error occurred while saving the comment Matt Hardwick
commented
Agreed, this should be a staple - competitors, even if the agent per se isn't branded put it in a branded folder/installer name makes it clear what it is and where it is from.
Matt Hardwick
supported this idea
·
-
57 votesMatt Hardwick
supported this idea
·
-
5 votesMatt Hardwick
supported this idea
·
-
18 votesMatt Hardwick
supported this idea
·
-
87 votesMatt Hardwick
supported this idea
·
I think we need to go one further and have multiple keys with the option to limit the scope per key. Want a R/W key, create one; want it limited to a specific customer, just select one customer, rather than all; need a read-only for all customers, create that and just don't tick write.