►
A
In
my
last
update,
I
talked
about
adding
a
mobile
devops
project
settings
page
with
the
first
iteration
focused
on
code
signing
today,
I'd
like
to
show
you
what
I've
been
working
on
on
my
screen.
I
have
a
draft
merge
request
to
work
out
how
we
can
decode
and
extract
relevant
information
from
code
signing
files.
A
The
first
example
here
is
a
provisioning
profile,
we'll
start
by
using
openssl
to
decode
the
file
which
will
give
us
back
a
plist
file.
P-List
files
are
a
bit
tricky
to
parse.
So
this,
mr,
has
a
gem
called
cf
property
list.
This
gem
does
a
nice
job
of
parsing
p-list
files
and
supports
multiple
ruby,
xml
libraries,
including
libxml
rexml
and
nokogiri,
using
cf
property
list,
we're
able
to
parse
the
plist
file
into
a
ruby
hash
and
easily
visualize
the
data
for
this
demo.
A
I
have
a
method
that
returns
a
representation
of
the
data
to
show
in
the
view,
but
since
this
data
doesn't
change,
I'm
planning
to
persist
it
to
the
database
when
the
file
is
uploaded.
This
will
speed
things
up
as
well.
Since
the
pricing
can
be
a
bit
slow
for
signing
certificates,
we
use
a
similar
process,
but
since
there
is
no
plist
embedded,
we
can
skip
that
step.
A
Putting
this
all
together
in
a
visualization,
I
have
a
bare
bones:
prototype
of
mobile
devops
settings,
page
that
visualizes
the
contents
of
provisioning
profiles
and
signing
certificates
for
provisioning
profile.
We
can
see
things
like
app
name
and
identifier,
the
team
name
and
identifier,
and
the
platforms
and
expiration
date
for
a
signing
certificate.
We
can
see
name
id
and
expiration
date
at
a
high
level.
This
information
is
helpful
because
it
gives
us
far
more
context
than
just
a
file
name.