Did you know that we released a new way to integrate Core Access with your target systems without a custom connector? Did you know it’s free? Join us to learn about how to use the Core Connector API to tie into your web-services or API enabled target systems.

1. Core
Connector
API

2. Presenters
Michael
Marks
Product
Manager,
Core
Security
Ravi
Mudaliyar
Development
Lead,
Core
Security

3. L E A R N M O R E
SPEAKER
NAME
Speaker
title,
company
name

4. AGENDA
• What
is
the
Connector
API?
• How
does
it
work?
• Demo
• Use
Cases
• Q&A

5. What
is
the
Connector
API?

6. Standard
and
Custom
Developed
Connectors
• Core
Security
developed
all
connectors
• Backlog
creates
wait
times
and
system
versioning
issues
Rapid
Development
Kit
• Develop
your
own
connector
• Requires
developers
and
specific
skill
set
Core
Connector
API
• Create
your
own
connector
• Easy
configuration
management
Core
Security’s
Connector
Strategy
</>
API

7. What
is
the
Core
Connector
API?
The
Core
Connector
API
is
a
Push
API
that
sends
workflow
information
from
Access
Assurance
Suite
to
a
request
handler.

8. How
does
it
work?

9. How
does
the
Core
Connector
API
work?
Target
SystemRequest
Handler
1.
AAS
triggers
a
workflow
for
a
target
system
configured
with
the
Connector
API.
2.
The
Core
Connector
API
pushes
the
information
to
the
request
handler.
3.
The
Request
Handler
receives
the
information
from
the
Core
Connector
API
and
“translates”
it
into
useful
information
for
the
target
system.
5.
The
requested
workflow
action
is
taken
on
the
target
system
Access
Assurance
Suite
4.
The
Request
Handler
hooks
into
the
target
system’s
web
services
or
API
to
initiate
the
change
on
the
account.

10. What
is
included
in
the
Core
Connector
API?
Subtitle
left
The
Core
Connector
API
Delivered
and
configured
like
any
other
connector.
Connector
API
Documentation
Detailed
technical
documentation,
covering
both
the
API
and
the
request
handler.
Sample
Request
Handler
Sample
request
handlers:
1.Written
in
Ruby,
connects
to
Debian
Linux
system
2.Written
in
Java,
connects
to
AD

11. Demo

12. Use
Cases

13. Airline
Organization
Upgrade
safe,
fast
deployments
• Multiple
target
systems
not
yet
integrated
• Didn’t
want
to
waste
time
or
money
on
custom
connectors
• Deployed
4
connectors
in
less
than
2
months
with
no
ProServ dollars
spent
• Upgrade
safe
from
both
AAS
and
target
systems

14. Healthcare
Organization
Complex
Directory
Integration
• SunOne Directory
Server
integration
• LDAP
connector
allows
you
to
select
1
objectClass when
configuring
the
connector
• Customer
wanted
to
select
multiple
special
objectClasses for
provisioning
• Deployed
Connector
API
request
handler
in
1/3 of
the
time
it
took
to
deploy
a
custom
connector

15. Q & A

16. THANK
YOU