push messaging service SNS instance called a topic Allows first lambda function to ‘notify’ second lambda function that it has been invoked, providing it with the same payload information that it receives from Slack
& recon times macOS version Security agents Are they installed, updated, and running? FileVault & SIP Status 32-bit apps and other Catalina considerations Core app versions Are they up to date?
channel_id = message["channel_id"] if channel_id != taniacomputer_channel_id: response_text = ":warning: `/jamf` can only be used from an authorized channel." response_json["text"] = response_text else: #etc...
channel_id = message["channel_id"] if channel_id != taniacomputer_channel_id: response_text = ":warning: `/jamf` can only be used from an authorized channel." response_json["text"] = response_text else: #etc...
channel_id = message["channel_id"] if channel_id != taniacomputer_channel_id: response_text = ":warning: `/jamf` can only be used from an authorized channel." response_json["text"] = response_text else: #etc...
verification token” Slack gives you a unique ‘signing secret’ string for your app Compute a HMAC-SHA256 hash of each request (using the signing secret as a base) And compare it to the hash value delivered in the request header, event["headers"]['X-Slack-Signature']
event["headers"]['X-Slack-Signature'] if hmac.compare_digest(expected_signature, delivered_sig): # Hooray, request came from Slack else: # Wah, this is an imposter message Verify Slack Signing Secret
event["headers"]['X-Slack-Signature'] if hmac.compare_digest(expected_signature, delivered_sig): # Hooray, request came from Slack else: # Wah, this is an imposter message Verify Slack Signing Secret
sensitive information into the Lambda code, use Amazon Secrets Manager to store: Jamf API credentials Slack signing secret Any other sensitive information Retrieve the values ‘on the fly’
message, but Slack best practice is 20 response_url can be used up to 5 times within 30 minutes of the command being invoked Provide a helper text for your slash command
feedback by completing the 2-question session survey in the JNUC 2019 app. UP NEXT Build a Second Generation 1-to-1 Student Device Program 2:45 - 3:30 p.m.