►
From YouTube: Showcasing Identity Manger and Nomios - André Cruz
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello:
everyone,
my
name
is
Andre
Cruz,
I'm
Sarah's,
our
on
grab
on
Twitter
and
I'm,
going
to
give
you
a
quick
demo
on
identity
management,
nom
use
so
really
quickly.
Identity
manager
is
an
identity
wallet
specification
and
that
really
embraces
open
standards
in
this
case
really
really
are
embracing
the
IDS
or
for
for
long.
The
centralized
identifiers
and
also
verifiable
credentials,
but
at
the
same
thing
that
we
are
seeing
today
is
that
I'll
to
throw
the
IDs
and
verify
the
credentials
are
mean
to
be
interoperable.
A
What
we
are
seeing
today
is
like
login
buttons,
such
as
continue
with
your
port,
continuing
with
blog
stack,
continuing
with
telecom,
which
is
very
similar
to
what
we
already
have
today,
with
sign-in
with
Google
Twitter
get
up
and
stuff
like
that.
So
what
is
means
for
developers
is
that
they
need
to
use
different
SDKs
to
integrate
into
their
websites,
which
is
really
you
know,
not
ideal,
because
the
underlying
technology
is
meant
to
be
standard
in
trouble.
Also
and
as
a
consequence.
A
What
happened
is
that,
because
developers
like
like
time,
they
end
up
taking
shortcuts
as
just
implements
a
few
of
those
and
me
as
a
developer.
I
need
to
really
create
different
identities.
There
are
conceptually
the
same
but
have
different
IDs.
So
when
I'm
like
replicating
the
my
data,
like
my
name
and
my
avatar
and
stuff
like
that
in
all
those
div
mechanisms
and
in
all
those
wallets
as
well,
so
what
Identity
Manager
aims
to
be
is
to
be
a
unified
entity,
wallet
that
aims
to
support
multiple,
the
IDs
and
the
other
methods
as
well.
A
So
let
me
just
quickly
showcase
IBM,
so
in
amuse,
so
we
have
here
very
early
early
draft
version
of
nominees,
which
has
some
features
that
I
want
to
show
you.
So
the
first
screen
that
you
you
see
here
is
the
setup
blocker
screen.
You
need
to
do
this
because
everything
within
a
wallet
is
encrypted,
so
you
must
choose
a
passphrase,
but
you
want
to
in
the
future,
want
to
support
other
lock
types,
such
as
your
touch
the
feature
within
your
MacBook
Pro
or
even
500
SV
devices
as
well.
A
So,
let's
just
put
a
password
here
and
continue
and
of
course
you
need
to
choose
the
idle
timer
so
that
it
locks
again
after
you
I
linked
for
some
time.
So,
let's
try
to
create
an
identity.
Ask
let's
start
create
a
unity
right
now,
so
you
just
choose
what
type
identity
you
are
a
person
or
an
organization
or
other.
A
Why
is
there
other?
Well,
because
even
your
cat
or
your
dog
should
have
an
identity,
because
your
dog
has
vaccines
and
stuff
like
that
that
you
want
to
keep
accelerated
to
to
to
your
your
pet.
Basically,
so,
let's
continue
and
let's
choose
like
type.
My
name
here
should
have
follow
as
well,
really
quickly
so
continue,
and
now
you
are
setting
up
your
device
name.
A
You
need
to
do
that
because
in
IDM
you
have
like
your
identity
and
you
can
have
multiple
devices
associated
with
it,
because
the
reality
is
is
that
you
use
your
device,
use
multiple
device
in
now
that
I
so
use
your
laptop,
your
desktop
your
mobile
phone
and
stuff,
like
that,
so
you
need
to
import
your
identity
I'll,
be
able
to
import
your
identity
in
multiple
devices.
So
what's
happening
now
is
that
IDM
right
now
supports
the
atom,
the
IP
ID,
the
ID
method
as
its
first,
the
ID
method.
A
But
we
want
when
to
support
others,
but
right
now
it's
creating
an
IP
NS
record
and
also
as
the
ID
document
and
type
NS
record
points
to
that
e
ID
documents,
and
we
fully
quickly
check
that
the
ID
document
and
its
context
content.
So
right
now
we
have
like
this
variable
called
IDM
wallet
which
is
exposed
just
for
development
and
in
this
case,
for
just
for
this
demo,
and
we
have
like
identities
list
and
let's
just
access
the
first
identity
and
get
it's
the
ID.
A
A
We
got
the
idea
document
rights
and
what
you
see
here
is
that
I
have
two
public
keys,
because
the
ID
documents
essentially
have
an
array
of
public
keys
that
you
can
change
over
time
and
in
this
case
I
have
my
master
key,
which
is
the
IP
NS
key
and
also
I
have
my
device.
This
device
key
in
my
D
ID
document
right
and
also
it's
important
to
mention
that
you
have
this
key
device
key
in
an
authentication
array,
meaning
that
this
device
can
be
used
for
authentication.
So,
let's
quickly
back
up
my
identity.
A
So
for
now
we
just
have
demonic
backup,
but
you
want
to
want
to
support
other,
more
user
friendly
backup
processes.
But
for
now
let's
just
go
to
rhythm
mnemonic,
so
I'm
going
to
copy
that
oh
I
forgot
to
copy
so
copy
to
clipboard,
and
just
put
it
there
for
now
and
go
through
so
I
need
to
select
the
tenth
words
so
dragon
I,
guess
and
the
third
word
will
be
fish
right
and
let's
continue
so
yeah.
A
It
is
secure.
It
means
that
my
master
key
was
removed
from
this
wallet
and
I'm
able
to
recover
it
by
using
that
minim
onic,
so
to
actually
show
you
that
Nam
use
is
just
user
interface
for
the
IDM
specification
in
wallet.
I
can
now
use
this
mini
Manik,
which
is
here
going
to
copy
it,
and
we
have
here
a
very
rough
version
of
another
wallet
that
uses
IDM
and
I'm
going
to
try
to
import
it
here.
A
All
right,
let's
wait
a
bit,
so
it's
resolving
IP
NS
records
already
so
now
it's
kind
of
replicating
replicating
the
stuff
that
I
have
my
other
device
to
to
this
device.
As
you
can
see,
it
already
finished
it
finish.
It
and
I
have
my
identity
there
with
my
photo.
So
the
funny
thing
is
that,
because
these
wallets
are
being
replicated,
I
can
just
edit
my
profile
and
things
kind
of
sync
seamlessly.
A
So
if
I
put
Portuguese
and
my
gender-
and
you
know
location
because
I'm
in
Spain
right
now,
I'm
gonna
put
Spain
and
save
it,
and
if
you
go
to
the
other
wallet
as
you
can
see,
it
already
replicated
really
fast.
So
and
actually
at
the
moment,
if
I
was
to
resolve
that
Eid
document
again,
we
will
see
another
public
key
there
right.
So
if
I
resolve
it
again,
it
takes
some
time.
A
Yes,
yeah,
sorry
there,
as
you
can
see,
it
has
three
public
keys
now,
because
the
water
wallet
generated
a
new
device
key
which
was
imported
into
your
GID
document.
That's
very
important
because
now
both
devices
can
be
used
for
the
idea,
tenth
occasion
and
signing
and
stuff
like
that,
so
let's
quickly
now
jump
to
two
features
of
IDM,
which
is
be
able
to
authenticate
to
an
it
up
and
also
to
sign
any
any
data
that
app
needs
to
sign.
A
So
we
have
like
this
very
drafty
example
shut
up
that
we
set
up
just
to
demonstrate
its
capabilities
really
so,
if
I
type
something
first,
of
course,
I
need
to
login
and
I
need
to
unlock
my
screen,
the
wallet
and,
if
I,
if
I,
accept
like
my
this
app.
This
shuttle
app
is
asking
me
to
send
my
personal
details
and
my
so
so
close.
So
if
I,
if
I
accept
I'm
now
logged
in
and
what
happened
is
that
the
wallet
created
a
session
between
between
the
up
and
the
wallet
itself
and
each
session
is
unique.
A
It
has
a
unique
ID
and
also,
if
I,
open
the
session
object.
You
see
that
the
identity,
the
ID
there
and
also
the
profile
details,
which
is
a
schema.org
person,
object
in
my
case
with
the
details
that
I've
filled
before
so
now.
I
can
type
messages
in
the
shot
and,
as
you
can
see
here,
you
have
like
a
check
mark.
It
means
that
I
produced
a
signature
that
was
validated
against
the
DLA
document.
Keys
public
key
is
one
of
them.
A
A
So
let
me
just
get
more
space
for
you
to
see
so
the
signature
itself
has
Adi
Adi
to
RL
there,
and
if
you
look
at
it,
it's
just
my
D
ID
and
the
fragment
pointing
to
the
public
key
that
was
used
to
sign,
but
because
I
used
the
session
key
to
sign
it's
not.
It
was
not
sign
with
my
device
private
key
directly,
but
instead
with
a
Shia
key,
which
is
basically,
we
call
that
the
session
key
so
session
keys
are
child
keys
off
of
the
devices
keys
and
to
to
derive
those
session
keys.
A
So,
if
you
don't
look
at
it,
we
have
like
signing
without
anything,
we
know
without
prompting
the
user
at
all
right.
So
this
is
all
happening
end
of
the
road.
The
trade-off
here
is
that
session
keys
are
not
while
they
are
not
stored
or
seen
by
the
app
it's
stored
on
the
wallet
in
plain
in
plain
raw
text.
This
means
that
they
are,
they
aren't
unencrypted.
A
So
this
means
that
for
use
cases
such
as
messages,
it's
fine,
but
if
you
need
more
security,
you
can
ask
to
sign
with
your
device
key
and
to
sign
with
your
device
key.
We
have
like
an
easter
egg
in
this
example,
shut
up.
If
you
type
like
something
that
contains
IP
Affairs
in
this
case
I'm
going
to
type
I
love
at
the
FS,
it
will
actually
prompt
to
sign
right
with
your
device
key
and
because
the
device
key
is
encrypted.
I
need
to
put
my
passphrase
there,
so
what
you
see
is
like
screen.
A
Okay,
something
is
wrong
with
with
the
scroll
bars,
but
just
ignore
it.
What
you
see
is
like
the
the
no
means
wallet
sort
in
this
case.
The
IDM
is
asking
me
to
authorize
the
signature
and,
as
you
can
see
you,
you
get
the
comment
there,
the
timestamp
so
I'm
going
to
sign
it
and
if
I
accept
the
see
the
same
kind
of
signature
was
produced,
but
that's
the
only
difference
is
that
the
key
part
is
actually
the
root
path.
A
So
it
means
that
there
is
no
need
to
derive
the
key,
because
the
device
private
key
was
directly
used
to
sign.
So,
as
you
can
see,
we
already
have
these
features,
which
is
very
useful
for
DUP
developers.
So,
basically
you
can
have
authentication
you
can
have
signing
either
with
your
session
keys
either
you
are
with
your
device
keys,
and
all
of
this
is
using
the
IDs
and
verifiable
credentials.
A
And,
lastly,
let
me
just
show
quickly
a
website
that
we
made
for
for
you
to
check
and
know
more
about
the
project.
So
we
have
like
Nam
just
go
to
Nam
use
that
I
know.
We
have
like
this
cool
website
that
you,
where
you
can
read
and
know
more
about
the
projects,
and
if
you
are
interested
you
can
actually
join.