Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
 Okta Administration Up and Running

You're reading from   Okta Administration Up and Running Drive operational excellence with IAM solutions for on-premises and cloud apps

Arrow left icon
Product type Paperback
Published in Dec 2023
Publisher Packt
ISBN-13 9781837637454
Length 306 pages
Edition 2nd Edition
Tools
Arrow right icon
Authors (2):
Arrow left icon
HenkJan de Vries HenkJan de Vries
Author Profile Icon HenkJan de Vries
HenkJan de Vries
Lovisa Stenbäcken Stjernlöf Lovisa Stenbäcken Stjernlöf
Author Profile Icon Lovisa Stenbäcken Stjernlöf
Lovisa Stenbäcken Stjernlöf
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Part 1:Getting Started with Okta
2. Chapter 1: IAM and Okta FREE CHAPTER 3. Chapter 2: Working with Universal Directory 4. Chapter 3: Using Single Sign-On for a Great End User Experience 5. Chapter 4: Increasing Security with Adaptive Multifactor Authentication 6. Chapter 5: Automating Using Lifecycle Management 7. Chapter 6: Customizing Your Okta GUI 8. Part 2: Extending Okta
9. Chapter 7: Okta Workflows 10. Chapter 8: API Access Management 11. Chapter 9: Managing Access with Advanced Server Access 12. Index 13. Other Books You May Enjoy

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...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime