mccormickt12 commented on code in PR #7803: URL: https://github.com/apache/hadoop/pull/7803#discussion_r2219822438
########## hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/AuthorizationContext.java: ########## @@ -0,0 +1,39 @@ +/** + * 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.hadoop.security; + +/** + * Utility for managing a thread-local authorization header for RPC calls. + */ +public final class AuthorizationContext { + private static final ThreadLocal<byte[]> AUTH_HEADER = new ThreadLocal<>(); + + private AuthorizationContext() {} + + public static void setCurrentAuthorizationHeader(byte[] header) { Review Comment: You can see the usage pattern in the tests a bit, but the caller would need to explicitly call this to set the auth header, possibly per call for our use case, but this supports the generalized case of one token per UGI too. But yes, this is a thread local context, its inspired by the caller context which uses the same pattern. Our expected use case is multiple tokens per UGI, each table would have its own token. -- 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: common-issues-unsubscr...@hadoop.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
