You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hubot cspp api revoke - revoke a specific token (optional)
hubot cspp api revoke all - revoke all tokens assigned to this id
The /api endpoint DELETE requires an API header: "X-API-KEY: $API_KEY"
To do that over slack, you'd have to know your key and paste it in there. I'd like to figure out a secure way to not have to specify the key but somehow use slack for the authentication.
An option would be to send something like X-SLACK-ID in the header, but that is very spoofable. This might mean we need some type of PSK for hubot and it does the header injection based on the slack envelop, but then there's a secret running in the bot that is effectively an admin on cspp.
Trying to think of other secure methods to make DELETE an easy request from the slack API.
Another options: The CSPP DMs you a generated code and you send that over or something?
The text was updated successfully, but these errors were encountered:
suggested syntax:
hubot cspp api revoke - revoke a specific token (optional)
hubot cspp api revoke all - revoke all tokens assigned to this id
The
/api
endpoint DELETE requires an API header: "X-API-KEY: $API_KEY"To do that over slack, you'd have to know your key and paste it in there. I'd like to figure out a secure way to not have to specify the key but somehow use slack for the authentication.
An option would be to send something like X-SLACK-ID in the header, but that is very spoofable. This might mean we need some type of PSK for hubot and it does the header injection based on the slack envelop, but then there's a secret running in the bot that is effectively an admin on
cspp
.Trying to think of other secure methods to make DELETE an easy request from the slack API.
Another options: The CSPP DMs you a generated code and you send that over or something?
The text was updated successfully, but these errors were encountered: