<!-- Please note this form is only for reporting bugs/suggesting missing tests/etc. If you require support please email certification@oidf.org - please include a link to the log-detail.html if your question is about a test failure. Please read the template carefully and include all the requested information. Reports with missing information will be assumed to be low priority. --> # What did you do? Run the SSF test suite against our SSF Transmitter implementation in authentik to check its validity. # What did you expect would happen? Tests to show me some misbehaving API endpoints # What did happen? - SSF Push tests failed due to a seeming deadlock, I was able to locally fix this with a patch, however I have no idea if this is the correct approach (this issue happens both with the SSF Transmitter and SSF Transmitter CAEP compat test profile): ```java - SSfPushRequest pushRequest = pushRequests.pollFirst(5, TimeUnit.SECONDS); + SSfPushRequest pushRequest = pushRequests.removeFirst(); ``` - The above deadlock also causes the ssf-push endpoint to not respond after a request has been sent, only responding when the dequee has been drained. - Ambiguity about the `aud` field when registering a stream. The spec says this value is supplied by the transmitter, however implementations such as the [sharedsignals.guide transmitter](https://github.com/duo-labs/sharedsignals/blob/21e76469ddc73e156c626bc2dde7efab1303bbfa/examples/transmitter/swagger_server/models.py#L170) make this an optional field and certain receivers (such as Apple business manager) require their own `aud` value to be used. - Ambiguity about the `verification_endpoint`, this is optional in the spec but required by the SSF Transmitter test suite, as otherwise the test will crash.