8000 Incorrect Reference in Custom Webhook Authentication Success Message · Issue #53 · jamf/JAWA · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Incorrect Reference in Custom Webhook Authentication Success Message #53

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
ball42 opened this issue May 12, 2025 · 0 comments
Open

Incorrect Reference in Custom Webhook Authentication Success Message #53

ball42 opened this issue May 12, 2025 · 0 comments
Assignees
@ball42
Labels
bug Something isn't working

Comments

@ball42
Copy link
Collaborator
ball42 commented May 12, 2025

Title: Incorrect Product Reference in Custom Webhook Authentication Success Message

Current Behavior

When creating or editing custom webhooks with custom authorization enabled, the success message incorrectly references Jamf Pro-specific instructions.

Expected Behavior

The success message should provide generic guidance since this section is for custom webhooks, not specifically for Jamf Pro webhooks.

Current Message

Copy and paste the following into the Header Authentication section of Jamf Pro webhooks:
 {'x-api-key': 'abc123'}

Suggested Message

Something more generic like:

Use the following in your request headers for authentication: 
{'x-api-key': 'abc123'}

Additional Context

  • Custom webhooks section is product-agnostic and should not contain Jamf Pro-specific instructions
  • This affects the UI message shown after successful custom webhook creation/editing
  • Only occurs when custom authorization option is selected

Impact

Users might be confused by the Jamf Pro-specific reference when working with custom webhooks that may be used with other systems.
@ball42 ball42 self-assigned this May 12, 2025
@ball42 ball42 added the bug Something isn't working label May 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ball42 ball42

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ball42
0