The document discusses the challenges faced by software developers in managing digital identities and provides solutions such as implementing OpenID 2.0 and OAuth 2.0 for federated identity management. It emphasizes building secure, scalable systems to facilitate user authentication and provides various programming libraries for developers. The conclusion advocates the use of open standards and user-driven trust models for better security and integration in digital identity management.

1. The
story
of
MITREid
Jus3n
Richer
The
MITRE
Corpora3on
© 2014 The MITRE Corporation. All rights reserved.
Approved for Public Release: Distribution Unlimited (Case Number: 14-1639)

2. The
plight
of
a
so;ware
developer
• I
build
things
that
people
use
• I
want
to
know
who’s
there
• What
can
I
do?

3. 1.
Make
local
accounts

4. 1.
Make
local
accounts

5. 1.
Make
local
accounts

6. 2.
Use
LDAP

7. 2.
Use
LDAP

8. 3.
Use
Enterprise
SSO

9. 3.
Use
Enterprise
SSO

10. 3.
Use
Enterprise
SSO
Firewall
Intranet
Internet

11. What
to
do?

12. Give
people
a
digital
iden3ty

13. Let’s
build
something
• OpenID
2.0
Server
• Running
on
corporate
IT
hardware
in
corporate
IT
environment
• Backed
by
corporate
SSO
and
user
profile
informa3on
• “We
do
SSO
so
you
don’t
have
to”

14. Why
OpenID?
• Open
standard
protocol
• Network-­‐based
federa3on
• User-­‐driven
trust
model
• Simple
to
use
and
develop

15. Make
it
easy
for
developers:
PlaXorm
support
• Libraries:
– Java
– PHP
– Python
– Javascript
– Ruby
– Perl
– …
• PlaXorms
&
Plugins:
– Spring
Security
– Elgg
– Wordpress
– Mediawiki
– Omniauth
– Drupal
– …

16. Usage
Profile:
The
prototype
Firewall
Intranet
Internet
OpenID Server
SSO

17. Usage
Profile:
The
external
service
Firewall
Intranet
Internet
OpenID Server
SSO

18. User
Profiles:
The
mobile
user
Firewall
Intranet
Internet
OpenID Server
2FA

19. The
architecture
Firewall
User Profiles
Shared
Database
Internal OP External OP
Intranet
Internet
Two-­‐Factor
Authn
Corporate
SSO

20. Run3me
security
decisions

21. Adop3on
by
the
extended
enterprise

22. The
Long
Tail
1
10
100
1000
10000

23. We
didn’t
even
plan
this

24. Mul3ple
types
of
user

25. Moving
on
from
OpenID
2.0

26. Let’s
build
it
(again)!
• OAuth
2.0
and
OpenID
Connect
server
• OpenID
Connect
client
library
• Enterprise-­‐friendly
features
and
plaXorm
• Flexible
deployment
and...

27. Open
Source

29. We’re
running
it
ourselves

30. Building
the
specifica3ons

31. Moving
toward
federa3on
across
the
extended
enterprise

32. Beaer
security:
Separa3on
OpenID
Provider

33. Delega3ng
services:
OAuth
OpenID
Provider

34. Beaer
security:
Revoca3on

35. Easier
integra3on
by
developers
OpenID
Provider• Standard
• Agile
• Flexible
• Distributed
• Proprietary
• Fragile
• Rigid
• Centralized

36. Beaer
administra3on:
An
abstrac3on
layer
OpenID
Provider

37. Scalable
security
decisions
Whitelist
Trusted partners, business contracts, customer
organizations, trust frameworks
Graylist
User-based trust decisions
Follow Trust on First Use model, keep logs
Blacklist
Very bad sites we don’t
want to deal with, ever
Organiza3ons
decide
these
End-­‐users
decide
these

38. Conclusions
• Use
open
standards
• Give
your
people
digital
iden33es
and
let
them
decide
where
to
use
them
• Use
federa3on
where
possible

39. Ques3ons?
jricher@mitre.org