John Pritchard (@indiapeloale), VP of Product & DevEcosystem @Okta)) talks developer concerns with authentication and identity, and how to manage 3rd-party integrations and cloud services.
**SHOW: 533CLOUD NEWS OF THE WEEK **- http://bit.ly/cloudcast-cnotw)**CHECK OUT OUR NEW PODCAST - **"CLOUDCAST BASICS")SHOW SPONSORS:
**CLOUD NEWS OF THE WEEK **- http://bit.ly/cloudcast-cnotw)**CHECK OUT OUR NEW PODCAST - ****"CLOUDCAST BASICS"**)
SHOW NOTES:
**Topic 1 - **Welcome to the show. Tell us about your background.
**Topic 2 - **Let’s begin by talking about the breadth of ways that Okta can now secure things for companies, applications, and developers. How do the pieces from Okta and (previously Auth0) fit together?
**Topic 3 - **As an application developer, where and when do I need to think about identity and authentication, and when is it a function of the infrastructure?
**Topic 4 - **Can you walk us through some common access and application patterns, so we have a better understanding of how many places that authentication, identity, access-mgmt come into play?
**Topic 5 - **From a bigger picture perspective, how do companies think about ownership and operations of these functional areas - do they own it, do they offload it to the cloud - what considerations do they need to make?
**Topic 6 - **How do developers typically engage with your teams and products/services? Do they need to be security experts first, or do you guide them through what to own and how Okta can offload core elements?
FEEDBACK?