Creating IAM Identity Providers

By Ashwin Venugopal -

 











Creating OpenID Connect (OIDC) Identity Providers

IAM OIDC Identity Providers are the entities describing an external identity provider (IdP) service that can easily support the OIDC standard and after creating them you must create one or more identity roles that can allow your organization's IdP to request temporary security credentials for access to AWS.

To create an IAM OIDC identity provider (Console)

  1. Firstly, register your application with the IdP to receive a client ID.
  2. Now, open the IAM console at https://console.aws.amazon.com/iam/.
  3. After that, select Identity Providers, and then Add provider in the navigation pane.
  4. Choose OpenID Connect for Configure provider.
  5. Now, you can type the URL of the IdP for Provider URL while complying with these restrictions- The URL must be case-sensitive, begin with https://, shouldn't contain a port number, and each OIDC identity provider must use a unique URL.
  6. Select Get thumbprint in order to verify the server certificate of your IdP.
  7. Type the client ID for Audience.
  8. You can also add key-value pairs for Add tags, in order to identify and organize your IdPs.
  9. Verify the provided information and then choose Add provider.
  10. Now, you can assign an IAM role to your identity provider to provide the external users identities managed by your identity providers permissions to access AWS resources in your account.

To add or remove a thumbprint for an IAM OIDC identity provider (console)

  1. Open the IAM console at https://console.aws.amazon.com/iam/.
  2. Choose Identity providers in the navigation pane and then, to be updated IAM identity provider's name.
  3. Now Manage in the Thumbprints section. You can also add or remove a thumbprint value here.
  4. After you are done, you can Save changes.

To remove an audience for an IAM OIDC identity provider (console)

  1. Choose Identity providers in the navigation pane and then, to be updated IAM identity provider's name.
  2. Select the radio button near the audience you want to remove in the Audiences section, then select Actions.
  3. Now, Remove audience to open a new window.
  4. Choose Remove to remove the audience.

To delete an IAM OIDC identity provider (console)

  1. Open the IAM console at https://console.aws.amazon.com/iam/.
  2. Choose Identity providers in the navigation pane and then, to be deleted IAM identity provider's check box.
  3. After confirming you wat to delete the provider by typing delete in the field, you can choose Delete.













Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different groups of computers, re
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning of alert rule parameter
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can query the log data stor
Read more