Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.

AEM - Architecture for an Okta Based Customer Identity and Access Management | AEM Community Blog Seeding

Avatar

Administrator

BlogImage.jpg

AEM - Architecture for an Okta Based Customer Identity and Access Management by Eddie Yao

Abstract

In today’s information-packed, multi-channel yet more and more regulated digital world, whether you just started a new business and are building your product, or you are a large business that has many applications, customer identity is always the fundamental and shared service in the application architecture. This is especially true in a cloud based architecture where you have multiple tenants in a distributed system. You need a unified customer identity solution to gain insights of your customers and provide them the best digital experience.

Okta as a SaaS Based Identity Platform
Among many workforce and customer identity solutions, platform services and integrations Okta offered as a SaaS, or Identity as a Service (IDaaS), solution, I will mainly focus on Authentication, Self Service Registration (SSR) and Authorization in the Customer Identity and Access Management (CIAM).

Okta not only offers a cloud based application for customer organizations to launch SSO applications and administrate the instance, it also provides multiple integration options (you will need to enable SSR if you use #1 and #2 below).
1. Okta Hosted Sign In Page
2. Sign In Widget
3. Custom UI with Okta SDK and API

Read Full Blog

AEM - Architecture for an Okta Based Customer Identity and Access Management

Q&A

Please use this thread to ask the related questions.



Kautuk Sahni
Topics

Topics help categorize Community content and increase your ability to discover relevant content.

0 Replies