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

no other libdefaults switch is working except forwardable #4

Open
piyushml20 opened this issue May 18, 2018 · 3 comments
Open

no other libdefaults switch is working except forwardable #4

piyushml20 opened this issue May 18, 2018 · 3 comments

Comments

@piyushml20
Copy link

Looks like libdefaults section of krb5.conf file only supports forwardable switch out of https://web.mit.edu/kerberos/krb5-devel/doc/admin/conf_files/krb5_conf.html. Just wanted to confirm if this is true.

@rtt-ncc
Copy link
Collaborator

rtt-ncc commented May 20, 2018

In the krb5.conf file that Berserko creates when you use the 'Create krb5.conf file', it only adds the forwardable switch to the [libdefaults] section.
However, if you manually added other switches to this section, then they should be picked up by the Java Kerberos libraries. I haven't had any cause to test this myself, but given that it picks up and actions the 'forwardable' flag I don't see why it would ignore other ones. I don't know which of the switches from the link you provide above are implemented by the Java Kerberos libraries though - maybe not all of them.

Is there something in particular that you are trying to do?

@piyushml20
Copy link
Author

piyushml20 commented May 21, 2018 via email

@rtt-ncc
Copy link
Collaborator

rtt-ncc commented May 22, 2018

Thanks for the further details!
OK, default_realm definitely won't work, because that is overridden by Berserko to be the 'Domain DNS Name' specified in the GUI. See the 'Setting Properties to Indicate the Default Realm and KDC' section at https://docs.oracle.com/javase/8/docs/technotes/guides/security/jgss/tutorials/KerberosReq.html.

I don't see any reason why the canonicalize flag would be ignored, but then I don't really know what it does.

Unfortunately Berserko doesn't yet cope well with more complex Kerberos configurations (which I'm guessing yours might be), in particular those that aren't based on Active Directory. And it can't yet handle cross-realm trusts ('domain trusts' in AD) due to limitations of the Java Kerberos libraries. I plan to add this support but haven't had time to do so yet.

Regards

Richard

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

No branches or pull requests

2 participants