voicesignin.com is a secure, 'voice first' authentication and identity platform that enables developers to build convenient personalized experiences within the ‘internet of voice’

1. The rationale for voicesignin.com
A voice first authentication platform

2. © Steven Bowden – bowdenCloud.com
voicesignin.com is a secure authentication
platform that enables developers to build
convenient personalised experiences within the
‘internet of voice’
tl;dr

3. • Currently done at the device level
• Natural Language Processing (NLP) struggles with non-
dictionary words such as emails, usernames and passwords
• Biometric approaches are prone to forgery
• Cumbersome multifactor PIN codes are often required
So how do we seamlessly establish an identity
across any internet connected voice or browser
based service?
© Steven Bowden – bowdenCloud.com
Authenticating on ‘voice first’ platforms is hard

4. © Steven Bowden – bowdenCloud.com
Such a system would have to be secure,
easy to use, browser compatible and
provide unique usernames that are
decipherable by NLP technology
Requirement

5. © Steven Bowden – bowdenCloud.com
Introducing the voicesignin.com identity
Version 1 username structure
The {color} {animal} of {USA place name}
(E.g. The brown bear of Chicago)

6. • The user signs in by saying this easy to remember username and
confirms by opening voicesignin.com and clicking a confirm button
• The username can be easily understood by NLP tools and will
supply several million combinations before there is a need for a
new phrase structure
• It is linked to a master identity (Facebook, Google ) via Auth0 and
managed in the browser at voicesignin.com
• Connections are made via the voicesignin.com platform enabling
API service thresholds and delays to be automatically enforced on
repeatedly failing authentication requests
How does it work?
© Steven Bowden – bowdenCloud.com

7. © Steven Bowden – bowdenCloud.com
User experience
User
App (voice or browser)
voicesignin.com platform
voicesignin.com
4. “I sent you a yellow
request, let me know
when you have
accepted”
2. Connect to the
brown bear of
Chicago
3. Confirming that
a yellow request
was sent
6. Does this user have
any requests?
7. The user has
this yellow
request
14. “You are
now signed in”
11. “I’ve accepted”
12. Check this
request status
13. It has been
accepted
5. View requests 8. Displays
yellow request
9. Tap yellow
button to accept
request
10. Yellow request has
been accepted
1. “I am the brown
bear of Chicago”
User effort

8. © Steven Bowden – bowdenCloud.com
Platform ecosystem
User
App (voice or browser)
voicesignin.com platform
voicesignin.comdeveloper.voicesignin.com
Developer

9. • Scalable serverless architecture
• AWS S3 for websites and profile storage
• Data encrypted at rest via AWS KMS
• Websites and APIs cached via AWS Cloudfront
• Built API first using AWS API Gateway
• Consumer and developer portals secured by Auth0 using
AWS API Gateway Custom Authorizors
• Developer APIs secured by AWS KMS generated keys and
AWS API Gateway Custom Authorizors
• Back-end logic carried out entirely by AWS Lambda
functions
© Steven Bowden – bowdenCloud.com
Platform infrastructure

10. S3 (user data encrypted at rest with KMS)
AWS API Gateway
User custom authorizer
(Lambda)
Developer custom
authorizer (Lambda)
Developer key custom
authorizer (Lambda)
Auth0
Auth0
S3/KMS
Application logic Lambda
Serverless platform architecture
Secure storage
Lambda Lambda
Authentication
Integration
LambdaLambda Lambda LambdaLambda Lambda
© Steven Bowden – bowdenCloud.com

11. • Developer portal ready on day 1
• Create a developer account
• Create a project
• Manage API keys
• GitHub repo with sample code
• API documentation
• The platform is free to use under the basic SLA and
premium features and pricing will be announced as the
platform grows
© Steven Bowden – bowdenCloud.com
Developers are the key to creating new
experiences from this platform

12. © Steven Bowden – bowdenCloud.com
Developer experience
Developer
developer.voicesignin.com
voicesignin.com platform
Developer’s app (voice or browser)
4. Display key
information
2. Provision project
keys
3. Return key
information
5. Test APIs
(optional)
6. Add key to
application config
1. Request project
keys
7. Add API call to request a
user connection
(establish session)
8. Add API call to check a
connection status
(maintain session)

13. Let’s get started!
https://voicesignin.com
https://developer.voicesignin.com
https://github.com/SteveBowden/voicesignin
© Steven Bowden – bowdenCloud.com