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

API terminology

There is some terminology that we need to go through to be able to understand all aspects of API management and API access management:

  • API product: An API product is an application comprising multiple API endpoints. These endpoints serve various needs and use cases but share a common authorization server. API products are what users log into using OIDC with an ID token.
  • API: APIs consist of endpoints that facilitate data exchange between systems based on requests and access permissions.
  • Authorization server: An authorization server is the heart of OAuth 2.0, generating access tokens by utilizing Okta’s scopes, claims, and access policies. In Okta, it’s common to create one server per API product, although multiple products can share one. The server is designed to address specific use cases rather than individual endpoints.
  • Scopes: Scopes are operations performed on your API endpoints. They are built into the application, and access...