/system/notifications/email returns nothing

[ccl0utier]

While testing the API, trying to get email notification settings from my configured pfSense returns nothing, despite everything else working perfectly well.

Did I miss anything?

pfSense Details

Community Edition

pfSense API Version

pfSense Notifications configuration

GET on endpoint: /api/v1/system/notifications/email returns:

CURL request details

❯ curl -v -s -k "Content-Type: application/json" -d '{"client-id": "61646d696e", "client-token": "<some_client_token>"}' -X GET https://pfsense/api/v1/system/notifications/email
* Closing connection -1
*   Trying 192.168.1.200...
* TCP_NODELAY set
* Connected to pfsense (192.168.1.200) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: C=CA; ST=QC; L=<REDACTED>; CN=pfsense
*  start date: Apr 21 20:17:08 2017 GMT
*  expire date: Apr 19 20:17:08 2027 GMT
*  issuer: C=CA; ST=QC; L=<REDACTED>
*  SSL certificate verify result: self signed certificate in certificate chain (19), continuing anyway.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x7f80ba00ca00)
> GET /api/v1/system/notifications/email HTTP/2
> Host: pfsense
> User-Agent: curl/7.64.1
> Accept: */*
> Content-Length: 79
> Content-Type: application/x-www-form-urlencoded
>
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
* We are completely uploaded and fine
< HTTP/2 200
< server: nginx
< date: Tue, 08 Feb 2022 14:12:00 GMT
< content-type: application/json
< referer: no-referrer
< strict-transport-security: max-age=31536000
< x-content-type-options: nosniff
<
{"status":"ok","code":200,"return":0,"message":"Success","data":[]}
* Connection #0 to host pfsense left intact
* Closing connection 0

[jaredhendrickson13]

Hey!

Thanks for pointing this out. Looks like this is a bug. The code is not populating the return data before the data is returned by the API. I'll have this patched in the next release this weekend.

Thanks!