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

Keberos principal set incorrectly? #36

Open
ashmeer7 opened this issue Aug 26, 2015 · 1 comment
Open

Keberos principal set incorrectly? #36

ashmeer7 opened this issue Aug 26, 2015 · 1 comment
Labels

Comments

@ashmeer7
Copy link

In at least one environment, we had to specify the principal name both via the Giraffe API and via sun.security.krb5.principal property.

@bluekeyes bluekeyes changed the title Kerberos: Don't set the principal in multiple places Keberos principal set incorrectly? Aug 26, 2015
@bluekeyes bluekeyes added the bug label Aug 26, 2015
@bluekeyes
Copy link
Member

I think this actually means that Giraffe is setting the principal property to the incorrect value. According to the javadoc the sun.security.krb5.principal property overwrites the value specified in the module by Giraffe.

Currently, Giraffe uses the username as the principal. In this environment, we know that the actual principal was different than the username. I suspect the code that failed passed the regular Linux username to Giraffe and then had to use the system property to specify the correct principal.

Giraffe should either clarify that it expects the principal instead of the username, or we should figure out how tools like SSH can automatically choose the correct principal (perhaps we shouldn't specify it at all, falling back to the system configuration).

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