ForgeRock (Open IDM) - Basic Understanding

Five main pillars of ForgeRock

  1. ForgeRock Identity Management
  2. ForgeRock Identity Management
  3. ForgeRock Directory Services
  4. ForgeRock Identity Gateway
  5. ForgeRock Open ICF (Connector Framework)
IAM (Identity & Access Management)

Identity Management mainly deals with:
  • Creating or onboarding identities into organization
  • Managing users digital identities and its life cycle
  • Here main goal is to provide right access to the right person
  • In Identity Management attributes are loaded to a identity and those are managed throughout the life cycle of user
Access Management mainly deals with:
  • Attributes which are loaded while identity management, now based on the value of these attribute's, here we takes decision in yes/no to allow or block that user from accessing that resource.

Basics of Access Management

  • Authentication - Its process of verifying Who you are? e.g. When you log on to Laptop with username and password, You are authenticating.
  • Authorization - It refers What you do? Verifying that you have specific access to do something

For hands-on you can download "Oracle VM Virtual box Manager" and install ForgeRock IDM
Also you can get download required binaries from below site and follow the steps: 
https://ktport.thinkific.com/courses/openam


Security Realm

In ForgeRock Identity Management (IDM), a Security Realm is a key concept that defines the security boundaries and authentication mechanisms used to protect resources and manage users within the system. A security realm is essentially a security domain within IDM where you can define how users are authenticated, authorized, and managed. Here's a breakdown of what it typically involves:

1. Authentication

  • The security realm determines how users authenticate to the system, including which identity stores (like LDAP, databases, or external identity providers) are used to verify user credentials.

2. Authorization

  • It also controls what resources users have access to once authenticated. This involves defining roles, permissions, and access control policies within the realm.

3. Identity Store

  • The realm is associated with an identity store, where user identities and their associated attributes are stored. This could be an internal database, an LDAP directory, or another type of identity store.

4. Configuration

  • You can configure realms to enforce specific security policies, such as password policies, session timeouts, and multi-factor authentication requirements.

5. Separation of Concerns

  • Security realms allow you to separate different groups of users or services within the same IDM instance. For example, you might have separate realms for different departments, regions, or types of users (e.g., internal employees vs. external partners).

6. Customization

  • Realms can be customized to support various authentication methods, such as username/password, OAuth2, SAML, or custom authentication modules.

In summary, a security realm in ForgeRock IDM is a configuration domain that governs how users are authenticated and authorized, and how their identities are managed within a specific security context.























Comments

Popular posts from this blog

SailPoint IIQ - Installation Steps

NIST (National Institute of Standards and Technology) Controls

SailPoint IIQ - Database Tables