Say in INTEGRATIONS.md what has been checked against a real osTicket
The ticket API was first verified with a test ticket (key and IP restriction, creation, message text arriving as written), then with a ticket opened for a real alert. A summary ticket (many problems at once) has not been seen on a real osTicket yet. Also records the two mistakes the real osTicket showed that the stand-in server had hidden: percent-encoded text, then base64. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
5386c1abe7
commit
c693600780
1 file changed
+7
-7
+7
-7
@@ -162,13 +162,13 @@ the dashboard views themselves load fine.
|
|||||||
"user" is this app, so an acknowledgement would only bounce) and osTicket's own staff alert on or off as you choose.
|
"user" is this app, so an acknowledgement would only bounce) and osTicket's own staff alert on or off as you choose.
|
||||||
- **What it can't do:** close, reopen, or comment on a ticket — osTicket's API has no such endpoint. A ticket opened
|
- **What it can't do:** close, reopen, or comment on a ticket — osTicket's API has no such endpoint. A ticket opened
|
||||||
here is yours to close in osTicket.
|
here is yours to close in osTicket.
|
||||||
- **Only partly verified against a real osTicket.** It was built from osTicket's published API documentation and
|
- **Checked against a real osTicket for a test ticket** (the API key with its IP restriction, creating the ticket, and the
|
||||||
tested against a stand-in server that checks what is sent (the key header, the JSON fields, the message encoding,
|
message arriving exactly as written, line breaks and non-ASCII characters included). It was built from osTicket's
|
||||||
and how each answer — created, refused key, bad request, redirect — is handled). Tickets sent to a
|
published API documentation and tested against a stand-in server too, and the real one showed two mistakes the stand-in
|
||||||
real osTicket first arrived with every space shown as `%20`, then as base64: osTicket takes the message's type from a
|
hid: the text first arrived with every space as `%20`, then as base64. osTicket takes the message's type from a
|
||||||
`data:` prefix but uses everything after the first comma exactly as it is, decoding nothing (its source and its own
|
`data:` prefix but uses everything after the first comma exactly as it is, decoding nothing, so the text is sent raw.
|
||||||
documented example agree). The text is now sent raw after the prefix (not yet re-checked against a real osTicket). If
|
A ticket opened for a real alert has been seen working too; a summary ticket (many problems at once) has not been seen on a real osTicket yet. If osTicket rejects a ticket, "Send a test
|
||||||
osTicket rejects a ticket, "Send a test ticket" shows the reason it gave.
|
ticket" shows the reason it gave.
|
||||||
|
|
||||||
### phpIPAM
|
### phpIPAM
|
||||||
|
|
||||||
|
|||||||
Reference in new issue
Block a user