This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

API Application Key Requires a Reference to an Active Tech's Username

mike.grim over 1 year ago

I am planning to make use of the WHD API and found that I can create an Application API key that is not tied to a specific Tech's account. However, when using the application API key, it requires you to submit a username of any enabled Tech account.

Since this is the case, I don't understand the functional difference between a Tech's private API key and an Application API key. If you can put in ANY Tech account username, what is the point of even asking for one?

Also, I would prefer to not have to tie our application to a specific Tech account. If they leave and their account is disabled, this would break the application. I would just use the 'admin' account, but we disable it to save a license. Will I need to therefore purchase a license to use the API for an internal application?

Thank you,

Mike

Parents

0 pabely over 1 year ago

I think the API should be tied to a TECH account for auditing purposes, we have used a specific Tech license for this and the username is "API" so yes consumes one of your licenses.
Cancel
Vote Up 0 Vote Down

Cancel
0 mike.grim over 1 year ago in reply to pabely

There is already a Tech API key functionality. You can certainly do that if you want.

However, the product has a somewhat poorly implemented application API key which is what most organizations would rather use for automation purposes. Using application keys is the standard and can be tied to an application if they want to audit the key's use. It is in no way less secure than tying it to a Tech account as long as you follow the appropriate standards.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 mike.grim over 1 year ago in reply to pabely

There is already a Tech API key functionality. You can certainly do that if you want.

However, the product has a somewhat poorly implemented application API key which is what most organizations would rather use for automation purposes. Using application keys is the standard and can be tied to an application if they want to audit the key's use. It is in no way less secure than tying it to a Tech account as long as you follow the appropriate standards.
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data