Unique Keys per Organization
complete
C
Cameron Granger
Ability to have unique keys per organization (similar in length/uniqueness to account keys) that can then be disabled in the event that a customer departs and the Huntress Account holder needs to disable the account.
If you give this an upvote, do us a favor and submit your use case! This will help us get things moving.
Matthiew Morin (Huntress)
updated the status to
complete
We just enabled the feature that will "revoke" Organization Keys when an Organization is deleted.
You can read more about the ins-and-outs of it in this KB article: https://support.huntress.io/hc/en-us/articles/54859813549843-Organization-Key-Revocation-After-Deletion
Thanks again for all the feedback!
B
Brad Schoolmeyer
yes we need to be able to re-enable it. This becomes a problem when there is a duplicate Organization. I can no longer easily delete the duplicate and reuse the key. I have other integrations in our RMM that use that key, so simply changing the key for Huntress would then break my other integrations.
Matthiew Morin (Huntress)
Brad Schoolmeyer: thanks for the feedback, we're going to look into improving that workflow. I knew that we would have to do it at some point, just wasn't sure how soon.
A
Adrian Perry
This is great, but please give us a way to re-enable/re-activate those Org Keys! Or at least make it a tick or toggle option when deleting the Org. Sometimes there's a legitimate requirement to remove an Org and re-use the key, which is now no longer possible!
Matthiew Morin (Huntress)
Adrian Perry: thanks for the feedback, we're going to look into improving that workflow. I knew that we would have to do it at some point, just wasn't sure how soon.
G
Greg Marchand
This is cool and all - But I think we were asking for the Account Key to be different per org - or that the Org key that does not exist generate a new Org without approval by an admin. basically, a way to lock it down if our account key gets shared because of a co-managed client
Matthiew Morin (Huntress)
updated the status to
complete
We just enabled the feature that will "revoke" Organization Keys when an Organization is deleted.
You can read more about the ins-and-outs of it in this KB article: https://support.huntress.io/hc/en-us/articles/54859813549843-Organization-Key-Revocation-After-Deletion
Thanks again for all the feedback!
Autopilot
Merged in a post:
Org Specific / Individual Account Keys for Agent Installation
M
Michael Kajewski
Currently to deploy an agent we need to use a global account wide "Account Key" along with an organisation key. The Org key doesn't matter as one is automatically created if the Account Key is correct, however should the account key gets exposed or left somewhere it shouldn't we would then need to rotate the account key and re-deploy our automations across ALL clients instead of just rotating the one that was exposed.
Can we please get a key per org or just individual keys for installation
G
Greg Marchand
Concur - We have several co-managed IT teams and have to give out our master key to do the install
G
Gary Herbstman
I agree with this and had recently been thinking about the same issue.
A
Alex Trout
Concur with this - we routinely need to give out both keys in co-managed scenarios. I'd prefer to have both the option to revoke org keys and the option to generate a unique keyset that can
only
be used by a specific org. I'd very much prefer to have the option to not
hand out an account key to co-managed customers.Matthiew Morin (Huntress)
updated the status to
in progress
Hi all, thanks for the feedback on this!
We're starting work on the ability to "revoke" or "invalidate" Organization Keys so that if an Agent attempts to register with the key, it will be denied.
This will prevent unexpected agent re-registrations and organization re-creations.
O
Orel Einy
This is a must-have as an MSSP to offboard customers or avoid abuse of a given organization key. Kindly promote this if possible.
Load More
→