Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
A
Android
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 6
    • Merge Requests 6
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

and though bugs are the bane of my existence, rest assured the wretched thing will get the best of care here

  • Confidential and Proprietary
  • NYNJA
  • Android
  • Wiki
  • TeleSign AutoVerify

TeleSign AutoVerify · Changes

Page history
Created TeleSign AutoVerify (markdown) authored May 10, 2017 by Marshall Taplits's avatar Marshall Taplits
Hide whitespace changes
Inline Side-by-side
Showing with 36 additions and 0 deletions
+36 -0
  • TeleSign-AutoVerify.md TeleSign-AutoVerify.md +36 -0
  • No files found.
TeleSign-AutoVerify.md 0 → 100644
View page @ 9d847f59
**Product Description**
https://www.telesign.com/products/auto-verify/
**SDK**
https://github.com/TeleSign/android_autoverify_sdk/
**Portal**
https://teleportal.telesign.com
marshall@nynja.biz / t5hnczvb888!
**Additional Information**
Your Customer ID is CF6E2918-89A9-417F-8074-382908FEDCD9. You are required to create a REST API secret key to be used when making requests. You can do so by visiting TelePortal at https://teleportal.telesign.com and clicking on Organization > View > Account Name.
Please refer to the REST API documentation for technical steps on how to integrate to our services. REST API documentation along with several SDKs can be found in TelePortal under the Support tab or by accessing https://developer.telesign.com/.
A few important things to note during integration:
API:
- Make sure you Base64 decode the API shared secret key before adding it in to the signature string
- Check that the elements of the signature string are in the order specified in the REST API
Connectivity:
- TeleSign only supports TLS v1.2 protocols, using the following ciphers:
- TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
- TLS_RSA_WITH_AES_128_GCM_SHA256
- TLS_RSA_WITH_AES_256_GCM_SHA384
- TLS_RSA_WITH_AES_128_CBC_SHA256
- TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
General:
- Make sure the posting URL field is configurable. We may request URL changes on occasion.
- Check that your application code is pointing to the TeleSign provided URL and not the IP address for the URL;
- Ensure your DNS infrastructure respects telesign.com<http://telesign.com> domain TTL value of 300 seconds
- Do not whitelist our URLs by IP on any device residing on your application's path to the Internet.
Your credentials are now active and you may begin integrating and using our services at any time. Per your agreement, you have a complimentary 30-day ramp up period which begins today, 05/08/2017 and ends 06/08/2017. Your billable cycle begins when your 5000 transactions expire. Please note, the billing email address on file is: marshall@nynja.biz
Clone repository
  • Android Test Cases
  • Bing Maps
  • FAQs
  • Home
  • Security checklist alfa
  • TeleSign AutoVerify
  • Voximplant FAQs