XJDKC commented on code in PR #2523: URL: https://github.com/apache/polaris/pull/2523#discussion_r2373228097
########## runtime/service/src/main/java/org/apache/polaris/service/identity/registry/DefaultServiceIdentityRegistry.java: ########## @@ -0,0 +1,144 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one + * or more contributor license agreements. See the NOTICE file + * distributed with this work for additional information + * regarding copyright ownership. The ASF licenses this file + * to you under the Apache License, Version 2.0 (the + * "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, + * software distributed under the License is distributed on an + * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + * KIND, either express or implied. See the License for the + * specific language governing permissions and limitations + * under the License. + */ + +package org.apache.polaris.service.identity.registry; + +import com.google.common.annotations.VisibleForTesting; +import jakarta.inject.Inject; +import java.util.EnumMap; +import java.util.Map; +import java.util.Optional; +import java.util.stream.Collectors; +import org.apache.polaris.core.context.RealmContext; +import org.apache.polaris.core.identity.ServiceIdentityType; +import org.apache.polaris.core.identity.dpo.ServiceIdentityInfoDpo; +import org.apache.polaris.core.identity.registry.ServiceIdentityRegistry; +import org.apache.polaris.core.identity.resolved.ResolvedServiceIdentity; +import org.apache.polaris.core.secrets.ServiceSecretReference; +import org.apache.polaris.service.identity.ServiceIdentityConfiguration; + +/** + * Default implementation of {@link ServiceIdentityRegistry} that resolves service identities from + * statically configured values (typically defined via Quarkus server configuration). + * + * <p>This implementation supports both multi-tenant (e.g., SaaS) and self-managed (single-tenant) + * Polaris deployments: + * + * <ul> + * <li>In multi-tenant mode, each tenant (realm) can have its own set of service identities + * defined in the configuration. The same identity will consistently be assigned for each + * {@link ServiceIdentityType} within a given tenant. + * <li>In single-tenant or self-managed deployments, a single set of service identities can be + * defined and used system-wide. + * </ul> + */ +public class DefaultServiceIdentityRegistry implements ServiceIdentityRegistry { + public static final String DEFAULT_REALM_KEY = ServiceIdentityConfiguration.DEFAULT_REALM_KEY; + public static final String DEFAULT_REALM_NSS = "system:default"; + private static final String IDENTITY_INFO_REFERENCE_URN_FORMAT = + "urn:polaris-secret:default-identity-registry:%s:%s"; + + /** Map of service identity types to their resolved identities. */ + private final EnumMap<ServiceIdentityType, ResolvedServiceIdentity> resolvedServiceIdentities; + + /** Map of identity info references (URNs) to their resolved service identities. */ + private final Map<String, ResolvedServiceIdentity> referenceToResolvedServiceIdentity; + + public DefaultServiceIdentityRegistry() { + this(new EnumMap<>(ServiceIdentityType.class)); + } + + public DefaultServiceIdentityRegistry( + EnumMap<ServiceIdentityType, ResolvedServiceIdentity> serviceIdentities) { + this.resolvedServiceIdentities = serviceIdentities; + this.referenceToResolvedServiceIdentity = + serviceIdentities.values().stream() + .collect( + Collectors.toMap( + identity -> identity.getIdentityInfoReference().getUrn(), + identity -> identity)); + } + + @Inject + public DefaultServiceIdentityRegistry( + RealmContext realmContext, ServiceIdentityConfiguration serviceIdentityConfiguration) { + this.resolvedServiceIdentities = + serviceIdentityConfiguration.resolveServiceIdentities(realmContext).stream() + .collect( + // Collect to an EnumMap, grouping by ServiceIdentityType + Collectors.toMap( + ResolvedServiceIdentity::getIdentityType, + identity -> identity, + (a, b) -> b, + () -> new EnumMap<>(ServiceIdentityType.class))); + + this.referenceToResolvedServiceIdentity = + resolvedServiceIdentities.values().stream() + .collect( + Collectors.toMap( + identity -> identity.getIdentityInfoReference().getUrn(), + identity -> identity)); + } + + @Override + public Optional<ServiceIdentityInfoDpo> discoverServiceIdentity( + ServiceIdentityType serviceIdentityType) { + ResolvedServiceIdentity resolvedServiceIdentity = + resolvedServiceIdentities.get(serviceIdentityType); + if (resolvedServiceIdentity == null) { + return Optional.empty(); + } + return Optional.of(resolvedServiceIdentity.asServiceIdentityInfoDpo()); + } + + @Override + public Optional<ResolvedServiceIdentity> resolveServiceIdentity( + ServiceIdentityInfoDpo serviceIdentityInfo) { + ResolvedServiceIdentity resolvedServiceIdentity = + referenceToResolvedServiceIdentity.get( + serviceIdentityInfo.getIdentityInfoReference().getUrn()); Review Comment: Similar to `UserSecretReference`: The reason we introduce a class for the reference can be found in this conversation: https://github.com/apache/polaris/pull/1305#discussion_r2036278251 Also shared the docstrings of the `UserSecretReference` here: ``` /** * Represents a "wrapped reference" to a user-owned secret that holds an identifier to retrieve * possibly remotely-stored secret material, along with an open-ended "referencePayload" that is * specific to an implementation of the secret storage and which is needed "unwrap" the actual * secret in combination with whatever is stored in the remote secrets storage. * * <p>Example scenarios: * * <p>If an implementation simply stores secrets directly in the secrets manager, the * referencePayload may be empty and "unwrapping" would be a simple identity/no-op transformation. * * <p>If tampering or corruption of secrets in the secrets manager presents a unique threat, an * implementation may use the referencePayload to ensure data integrity of the secret by storing a * checksum or hash of the stored secret. * * <p>If the system must protect against independent exfiltration/attacks on a dedicated secrets * manager and the core persistence database, the referencePayload may be used to coordinate * secondary encryption keys such that the original secret can only be fully "unwrapped" given both * the stored "secret material" as well as the referencePayload and any associated keys used for * encryption. */ ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
