Distil SDK FAQs

How does the SDK impact jailbroken devices?

You can decide whether to monitor or block jailbroken or rooted devices using the Mobile Policy settings in the Distil Portal.


How is the Distil SDK actually deployed and what do I need to do from my side?

The SDK uses the existing Distil platform and is deployed in our existing deployment options. You only need an instance of Distil protecting your domain, in addition to integration of the Distil SDK library with your app.


How is the token requested and where is the key provided?

Token requests are completely transparent and are handled by the Distil SDK.


What happens if the SDK fails to receive the token? What if the SDK fails to retrieve the token?

The SDK uses the same channel as the mobile app. As long as the Distil edge node is online, it will retrieve the token. If the edge node goes offline, all traffic is sent directly to the customer’s origin server.


Is the edge node location embedded in the SDK? Or is it something that can be configurable?

The edge node is not embedded. The SDK sends a request under your URL, which is captured by our edge node.


How do you distribute your SDK releases?

We distribute the SDK on request. Simply ask your AE for your unique Distil SDK version.


What is the estimated latency?

The SDK requests a new token every five (5) minutes to prevent each API request from requesting a token. Therefore, there is no latency—unless an API request happens when a new token is required. The entire challenge<>response and token request process takes well below one (1) second.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request