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

Managing your ASA environment

Now that we have established our first setup in ASA, and we understand how ASA works from a project perspective, let’s dive into other management parts of ASA. For instance, what else can we manage within a project, how do we manage groups and users, and how do we allow users to have access?

Managing projects

In the previous section, we created a project so that we could create an enrollment token. If you want to secure anything in ASA, you will need a token. The project is used to connect a set of resources with a set of configurations. You can compare it to a domain in AD. The project will let you manage different kinds of servers or web applications. So, after you have created your project, as you did to create the enrollment token for a server, you want to add groups to it. But before we can do that, we have to create a group. Once you have integrated ASA with Okta using System for Cross-Domain Identity Management (SCIM), you can sync...