Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Security #4

Open
fabianrbz opened this issue Jun 18, 2017 · 14 comments
Open

Security #4

fabianrbz opened this issue Jun 18, 2017 · 14 comments
Assignees
Labels
Milestone

Comments

@fabianrbz
Copy link
Owner

No description provided.

@fabianrbz fabianrbz added this to the Labs milestone Jun 18, 2017
@fabianrbz fabianrbz self-assigned this Jun 18, 2017
@fabianrbz
Copy link
Owner Author

@HorizonNet would a self-signed certificate work for this?

@HorizonNet
Copy link
Collaborator

Why do you need a certificate?

@fabianrbz
Copy link
Owner Author

as part of https://www.cloudera.com/documentation/enterprise/5-9-x/topics/cm_sg_intro_kerb.html
it says that we need to configure tls encryption for cloudera manager, and in order to do that we need a certificate.

@HorizonNet
Copy link
Collaborator

TLS encryption is not part of the Kerberos setup as described in the lab. TLS is part of level-security for CM server and agents, which are out of scope. The hint in the Cloudera documentation just says that Kerberos alone is not enough for a secure cluster.

@fabianrbz
Copy link
Owner Author

@HorizonNet I'm using aws with elastic IPS for the cluster. Should I use the private DNS and IPS for KDC or the public ones?

@HorizonNet
Copy link
Collaborator

You should never rely on IPs in a cluster. On AWS it is best to stick with the private hostnames. This prevents additional traffic costs and allows some advanced security configurations.

@fabianrbz
Copy link
Owner Author

@HorizonNet thanks, but do i need to map the private hostnames to their private or public ips in the /etc/hosts or should work out of the box?

@HorizonNet
Copy link
Collaborator

On AWS using private hostnames only works out of the box. You shouldn't need to touch /etc/hosts at all.

@fabianrbz
Copy link
Owner Author

@HorizonNet I'm getting a kprop: Connection refused while connecting to server when trying to propagate the db as described here. According to the installation steps we shouldn't start krb5kdc until after the database is propagated. But how would the slave get the db if the daemon is not running?

@HorizonNet
Copy link
Collaborator

Why are you trying to set up multiple KDCs?

@fabianrbz
Copy link
Owner Author

fabianrbz commented Jun 20, 2017

I thought that the idea was to have a master in one of the hosts and a client/slave in each host. how should we setup the KDC then?

@HorizonNet
Copy link
Collaborator

You need to set up a central KDC and a Kerberos client on each host. The client is not part of the KDC. It only uses the KDC. You only have a master/slave architecture if you set up high availability for your KDC (which is what your link describes).

@fabianrbz
Copy link
Owner Author

@HorizonNet unrelated question, is it mandatory to take the challenge or we can just take the exam?

@HorizonNet
Copy link
Collaborator

The challenge is mandatory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants