Book Image

Okta Administration Up and Running - Second Edition

By : HenkJan de Vries, Lovisa Stenbäcken Stjernlöf
Book Image

Okta Administration Up and Running - Second Edition

By: HenkJan de Vries, Lovisa Stenbäcken Stjernlöf

Overview of this book

Identity and access management (IAM) is a set of policies and technologies used to ensure an organization’s security, by carefully assigning roles and access to users and devices. This book will get you up and running with Okta, an IAM service that can help you manage both employees and customers. The book begins by helping you understand how Okta can be used as an IAM platform, before teaching you about Universal Directory and how to integrate with other directories and apps, as well as set up groups and policies for Joiner, Mover, and Leaver flows. This updated edition helps you to explore agentless desktop single sign-on (SSO) and multifactor authentication (MFA) solutions, and showing how to utilize Okta to meet NIST requirements. The chapters also walk you through Okta Workflows, low-/no-code automation functionalities, and custom API possibilities used to improve lifecycle management. Finally, you’ll delve into API access auditing and management, where you’ll discover how to leverage Advanced Server Access (ASA) for your cloud servers. By the end of this book, you’ll have learned how to implement Okta to enhance your organization's security and be able to use the book as a reference guide for the Okta certification exam.
Table of Contents (14 chapters)
1
Part 1:Getting Started with Okta
8
Part 2: Extending Okta

What Okta Workflows is

When we talk about Workflows and Okta, we typically look at the separate no-code console we find in Okta (more on that later). However, we can also work with different types of hooks; let’s look at these first.

Using workflow capabilities

The workflow capabilities within Okta expand across three areas – inline hooks, event hooks, and automation. These areas have different functionalities and different options.

Inline hooks

With inline hooks, you can call your own custom code with help from Okta’s REST API. The outbound calls are triggered by events in your Okta process flows. Your custom code will be a web service with an internet-accessible endpoint. The service isn’t hosted by Okta; it’s hosted by you. The inline hooks use synchronous calls, which means that the process that triggered the hook/outbound call is paused until it receives an answer from your service.

So, how are these hooks added? Let’s look...