Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
0.5-incubating
-
None
-
None
-
None
Description
Deploy a secure cluster and check the /etc/atlas/conf/client.properties. It still has some placeholder values for all the settings..
These properties are used by AtlasClient.java and with secure deployment these values are invalid and results in unexpected results..
Client.properties snapshot from a kerberized cluster.
os-s11-testing-3-atlas-1:~ # cat /etc/atlas/conf/client.properties # # 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. # ######### Security Properties ######### # SSL config atlas.enableTLS=false truststore.file=/path/to/truststore.jks cert.stores.credential.provider.path=jceks://file/path/to/credentialstore.jceks # following only required for 2-way SSL keystore.file=/path/to/keystore.jks # Authentication config # enabled: true or false atlas.http.authentication.enabled=false # type: simple or kerberos atlas.http.authentication.type=simple ######### Security Properties ######### os-s11-testing-3-atlas-1:~ #
Attachments
Attachments
Issue Links
- is duplicated by
-
ATLAS-363 Kerberized cluster: client.properties does not have correct values for the properties
- Resolved
- links to