is it customisable with third party apps ?

We do respect privacy of every user and we are trying to make our solution GDPR compliant. Because we are trying to protect customers from getting scammed by the calls.

[quote='894518022, DTS Engineer, /thread/827166?answerId=894518022#894518022'] You still need to implement the authentication service, which is that that URL is "for". See "Anonymous Authentication" for an overview of that's involved. [/quote] @DTS Engineer This link is not working, do we have any sample service or documentation. So that we can refer it for an implementation purpose,

Thanks for your answer. [quote='894297022, DTS Engineer, /thread/827166?answerId=894297022#894297022'] I'm not sure I understand this. Are you not planning to use any sort of authentication for your user(s)? I'm not sure the protocol can function without this. [/quote] No we are having PIR issuer token, currently passing directly to the framework. I am asking about field in the form for Privacy Pass Token Issuer URL. Because we reusing example PIR server from apple and not sure whether it has implementation for token URL or not to mention this in the form.

Can we keep Privacy Pass Token Issuer URL empty as we have not implemented anything for this ?

Hello @RomainDropB, Nice to hear that you managed to run the filter. One thing I wanted to confirm about pirPrivacyPassIssuerURL. What is required to be passed for this parameter, did you implement any infrastructure for this ?

@DTS Engineer I see there is a change in then entitlement request for NEURLFilter https://icloud.developer.apple.com/dashboard/identity/teams/9N738HVC7M/neurl-filter-form. I see previously Validation Test DNS Record section was asking for Update your domain DNS records. Add apple-url-filter=<bundle_identifier>, where <bundle_identifier> is replaced with your app bundle ID but in new flow they are asking where <bundle_identifier> is replaced with your extension's bundle identifier. Please confirm If we need extension's bundle ID or only app's bundle ID

@DTS Engineer So is it a restriction from apple side that is gone block/reject this entitlement request or is it a suggestion from your end in order to reduce the complexity and inter dependency.

any update @DTS Engineer

One thing I wanted to confirm, suppose i submit one request to onboard OHTTP relay for our organisation app and it gets approved, so can I re submit the request with different bundle ID and same PIR server, OHTTP server ?

@KayleeSC I got below feedback from Apple 1️⃣ Checking DNS TXT record for protectus-pirservice-iso-dfcxfmbkghc9a7hu.northeurope-01.azurewebsites.net... ✗ DNS TXT record is missing or incorrect Expected: "apple-url-filter=com.example.apple-samplecode.SimpleURLFilter3978B9P5X5" 2️⃣ Checking OHTTP Gateway SSL/TLS configuration for protectus-ohttp-gateway-gqdqa3hackhcf9c3.northeurope-01.azurewebsites.net... ✗ HTTP/2 (h2) protocol is NOT supported ✓ Certificate chain appears valid ✓ SSL/TLS connection successful 3️⃣ Checking OHTTP key configuration at https://protectus-ohttp-gateway-gqdqa3hackhcf9c3.northeurope-01.azurewebsites.net... ✗ Failed to fetch OHTTP keys: HTTP 404 Please see https://swiftpackageindex.com/apple/pir-service-example/main/documentation/pirservice/onboarding to learn more about the requirements and OHTTP.

@KayleeSC I mean before submitting request, how did you make sure that everything is as expected. We have 2 different things PIR service and OHTTP gateway.

@KayleeSC For PIR server, did you created new one or reused https://github.com/apple/pir-service-example/tree/main/Sources before submitting OHTTP form, have you done any special kind of configuration for backend PIR service. Because my OHTTP form is been rejected by apple, may be it will be a great help if you can provide some checklist

@DTS Engineer That is great.

@DTS Engineer will I get approval for OHTTP relay onboarding on the mail itself ? and if you have access to the request please let us know the status of that ?