<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Identity and Access Management on SILO</title><link>https://silo.pgsty.com/administration/identity-access-management/</link><description>Recent content in Identity and Access Management on SILO</description><generator>Hugo</generator><language>en</language><atom:link href="https://silo.pgsty.com/administration/identity-access-management/index.xml" rel="self" type="application/rss+xml"/><item><title>User Management</title><link>https://silo.pgsty.com/administration/identity-access-management/minio-user-management/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://silo.pgsty.com/administration/identity-access-management/minio-user-management/</guid><description>&lt;p&gt;&lt;a id="user-management"&gt;&lt;/a&gt;
&lt;a id="minio-users"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;A MinIO user consists of a unique access key (username) and corresponding secret key (password). Clients must authenticate their identity by specifying both a valid access key (username) and the corresponding secret key (password) of an existing MinIO user.&lt;/p&gt;
&lt;p&gt;Each user can have one or more assigned &lt;a href="https://silo.pgsty.com/administration/identity-access-management/policy-based-access-control/#minio-policy"&gt;policies&lt;/a&gt; that explicitly list the actions and resources to which that user has access. Users can also inherit policies from the &lt;a href="https://silo.pgsty.com/administration/identity-access-management/minio-group-management/#minio-groups"&gt;groups&lt;/a&gt; in which they have membership.&lt;/p&gt;</description></item><item><title>Group Management</title><link>https://silo.pgsty.com/administration/identity-access-management/minio-group-management/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://silo.pgsty.com/administration/identity-access-management/minio-group-management/</guid><description>&lt;p&gt;&lt;a id="group-management"&gt;&lt;/a&gt;
&lt;a id="minio-groups"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;A &lt;em&gt;group&lt;/em&gt; is a collection of &lt;a href="https://silo.pgsty.com/administration/identity-access-management/minio-user-management/#minio-users"&gt;users&lt;/a&gt;. Each group can have one or more assigned &lt;a href="https://silo.pgsty.com/administration/identity-access-management/policy-based-access-control/#minio-policy"&gt;policies&lt;/a&gt; that explicitly list the actions and resources to which group members are allowed or denied access.&lt;/p&gt;
&lt;p&gt;For example, consider the following groups. Each group is assigned a &lt;a href="https://silo.pgsty.com/administration/identity-access-management/policy-based-access-control/#minio-policy-built-in"&gt;built-in policy&lt;/a&gt; or supported &lt;a href="https://silo.pgsty.com/administration/identity-access-management/policy-based-access-control/#minio-policy-actions"&gt;policy action&lt;/a&gt;. Each group also has one or more assigned users. Each user’s total set of permissions consists of their explicitly assigned permission &lt;em&gt;and&lt;/em&gt; the inherited permissions from each of their assigned groups. MinIO by default &lt;em&gt;denies&lt;/em&gt; access to any resource or operation not explicitly allowed by a user’s assigned or inherited policies.&lt;/p&gt;</description></item><item><title>OpenID Connect Access Management</title><link>https://silo.pgsty.com/administration/identity-access-management/oidc-access-management/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://silo.pgsty.com/administration/identity-access-management/oidc-access-management/</guid><description>&lt;p&gt;&lt;a id="openid-connect-access-management"&gt;&lt;/a&gt;
&lt;a id="minio-external-identity-management-openid-access-control"&gt;&lt;/a&gt;
&lt;a id="minio-external-identity-management-openid"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;MinIO supports using an OpenID Connect (OIDC) compatible IDentity Provider (IDP) such as Okta, KeyCloak, Dex, Google, or Facebook for external management of user identities.&lt;/p&gt;
&lt;p&gt;For identities managed by the external OpenID Connect (OIDC) compatible provider, MinIO can use either of two methods to assign policies to the authenticated user.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Use the &lt;a href="https://datatracker.ietf.org/doc/html/rfc7519#section-4"&gt;JSON Web Token claim&lt;/a&gt; returned as part of the OIDC authentication flow to identify the &lt;a href="https://silo.pgsty.com/administration/identity-access-management/policy-based-access-control/#minio-policy"&gt;policies&lt;/a&gt; to assign to the authenticated user.&lt;/li&gt;
&lt;li&gt;Use the &lt;code&gt;RoleArn&lt;/code&gt; specified in the authorization request to assign the policies attached to the provider’s RolePolicy.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;MinIO by default denies access to all actions or resources not explicitly allowed by a user’s assigned or inherited &lt;a href="https://silo.pgsty.com/administration/identity-access-management/policy-based-access-control/#minio-policy"&gt;policies&lt;/a&gt;. Users managed by an OIDC provider must specify the necessary policies as part of the JWT claim. If the user JWT claim has no matching MinIO policies, that user has no permissions to access any action or resource on the MinIO deployment.&lt;/p&gt;</description></item><item><title>Active Directory / LDAP Access Management</title><link>https://silo.pgsty.com/administration/identity-access-management/ad-ldap-access-management/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://silo.pgsty.com/administration/identity-access-management/ad-ldap-access-management/</guid><description>&lt;p&gt;&lt;a id="active-directory-ldap-access-management"&gt;&lt;/a&gt;
&lt;a id="minio-external-identity-management-ad-ldap"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;MinIO supports configuring a single Active Directory or LDAP (AD/LDAP) service for external management of user identities. Enabling AD/LDAP external identity management disables the &lt;a href="https://silo.pgsty.com/administration/identity-access-management/minio-identity-management/#minio-internal-idp"&gt;MinIO internal IDP&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;For identities managed by the external AD/LDAP provider, MinIO uses the user’s Distinguished Name and attempts to map it against an existing &lt;a href="https://silo.pgsty.com/administration/identity-access-management/policy-based-access-control/#minio-policy"&gt;policy&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;If the AD/LDAP configuration includes the necessary settings to query the user’s AD/LDAP group membership, MinIO &lt;em&gt;also&lt;/em&gt; uses those group Distinguished Names and attempts to map each against an existing &lt;a href="https://silo.pgsty.com/administration/identity-access-management/policy-based-access-control/#minio-policy"&gt;policy&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>MinIO External Identity Management Plugin</title><link>https://silo.pgsty.com/administration/identity-access-management/pluggable-authentication/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://silo.pgsty.com/administration/identity-access-management/pluggable-authentication/</guid><description>&lt;p&gt;&lt;a id="minio-external-identity-management-plugin"&gt;&lt;/a&gt;
&lt;a id="id1"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;The MinIO Identity Management Plugin provides a REST interface for offloading authentication to an external identity manager through a webhook service.&lt;/p&gt;
&lt;p&gt;Once enabled, client applications use the &lt;code&gt;AssumeRoleWithCustomToken&lt;/code&gt; STS API extension to generate access tokens for MinIO. MinIO verifies this token by making a POST request to the configured plugin endpoint and uses the returned response to determine the authentication status of the client.&lt;/p&gt;
&lt;h2 id="configuration-settings"&gt;Configuration Settings&lt;/h2&gt;
&lt;p&gt;You can configure the MinIO Identity Management Plugin using the following environment variables or configuration settings:&lt;/p&gt;</description></item><item><title>Access Management</title><link>https://silo.pgsty.com/administration/identity-access-management/policy-based-access-control/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://silo.pgsty.com/administration/identity-access-management/policy-based-access-control/</guid><description>&lt;p&gt;&lt;a id="access-management"&gt;&lt;/a&gt;
&lt;a id="minio-policy"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;MinIO uses Policy-Based Access Control (PBAC) to define the authorized actions and resources to which an authenticated user has access. Each policy describes one or more &lt;a href="https://silo.pgsty.com/administration/identity-access-management/policy-based-access-control/#minio-policy-actions"&gt;actions&lt;/a&gt; and &lt;a href="https://silo.pgsty.com/administration/identity-access-management/policy-based-access-control/#minio-policy-conditions"&gt;conditions&lt;/a&gt; that outline the permissions of a &lt;a href="https://silo.pgsty.com/administration/identity-access-management/minio-user-management/#minio-users"&gt;user&lt;/a&gt; or &lt;a href="https://silo.pgsty.com/administration/identity-access-management/minio-group-management/#minio-groups"&gt;group&lt;/a&gt; of users.&lt;/p&gt;
&lt;p&gt;MinIO PBAC is built for compatibility with AWS IAM policy syntax, structure, and behavior. The MinIO documentation makes a best-effort to cover IAM-specific behavior and functionality. Consider deferring to the &lt;a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/"&gt;IAM documentation&lt;/a&gt; for more complete documentation on AWS IAM-specific topics.&lt;/p&gt;</description></item><item><title>MinIO External Access Management Plugin</title><link>https://silo.pgsty.com/administration/identity-access-management/pluggable-authorization/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://silo.pgsty.com/administration/identity-access-management/pluggable-authorization/</guid><description>&lt;p&gt;&lt;a id="minio-external-access-management-plugin"&gt;&lt;/a&gt;
&lt;a id="id1"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;The MinIO Access Management Plugin provides a &lt;code&gt;REST&lt;/code&gt; interface for offloading authorization through a webhook service.&lt;/p&gt;
&lt;p&gt;Once enabled, MinIO sends the request and credential details for every API call to the configured external HTTP(S) endpoint and looks for a response of &lt;code&gt;ALLOW&lt;/code&gt; or &lt;code&gt;DENY&lt;/code&gt;. MinIO can therefore delegate the access management to the external system instead of relying on S3 &lt;a href="https://silo.pgsty.com/administration/identity-access-management/policy-based-access-control/#minio-policy"&gt;policy based access control&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id="configuration-settings"&gt;Configuration Settings&lt;/h2&gt;
&lt;p&gt;You can configure the MinIO External Access Management Plugin using the following environment variables or configuration settings.&lt;/p&gt;</description></item></channel></rss>