You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Siyao Meng (Jira)" <ji...@apache.org> on 2022/02/23 05:59:00 UTC
[jira] [Updated] (HDDS-6366) [Multi-Tenant] Disable specifying custom accessId in OzoneManager
[ https://issues.apache.org/jira/browse/HDDS-6366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siyao Meng updated HDDS-6366:
-----------------------------
Description:
Disable client's ability to specify custom accessId in OzoneManager, for now.
Enforce a check that the accessId must be {{tenantId$username‘‘ in {{OMAssignUserToTenantRequest}} when checking accessId validity
was:Disable client's ability to specify custom accessId in OzoneManager, for now.
> [Multi-Tenant] Disable specifying custom accessId in OzoneManager
> -----------------------------------------------------------------
>
> Key: HDDS-6366
> URL: https://issues.apache.org/jira/browse/HDDS-6366
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Siyao Meng
> Priority: Major
>
> Disable client's ability to specify custom accessId in OzoneManager, for now.
> Enforce a check that the accessId must be {{tenantId$username‘‘ in {{OMAssignUserToTenantRequest}} when checking accessId validity
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org