Book Image

Okta Administration: Up and Running

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

Okta Administration: Up and Running

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

Overview of this book

IAM, short for identity and access management, is a set of policies and technologies for ensuring the security of an organization through careful role and access assignment for users and devices. With this book, you’ll get up and running with Okta, an identity and access management (IAM) service that you can use for both employees and customers. Once you’ve understood how Okta can be used as an IAM platform, you’ll learn about the Universal Directory, which covers how to integrate other directories and applications and set up groups and policies. As you make progress, the book explores Okta’s single sign-on (SSO) feature and multifactor authentication (MFA) solutions. Finally, you will delve into API access management and discover how you can leverage Advanced Server Access for your cloud servers and Okta Access Gateway for your on-premises applications. By the end of this Okta book, you’ll have learned how to implement Okta to enhance your organization's security and be able to use this book as a reference guide for the Okta certification exam.
Table of Contents (13 chapters)
1
Section 1: Getting Started with Okta
8
Section 2: Extending Okta

API Access Management administration

So, let's go into the Okta administrator panel to set up some of the features that were examined in the last section. Navigate to Security | API. Here, we see that we have three tabs we can work with:

  • Authentication Servers
  • Tokens
  • Trusted Origins

This is what it looks like in the admin panel:

Figure 7.3 – Available tabs for API management

As we already spoke about Tokens and Trusted Origins earlier in this chapter, we will now only focus on Authorization Servers. If you don't have the API Access Management product enabled, you will only see this menu for the default org authorization server, explained next.

Authorization server

To start off, we need to look at why you might need an authorization server. An authorization server is basically something to create and solidify (or mint, as it's normally called) Oauth 2.0 or OpenID Connect tokens. You can use it for authentication...