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.

Sign up for GitHub

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

Jump to bottom

Support kerberos #264

Open
stdweird opened this issue Mar 22, 2017 · 2 comments
Open

Support kerberos #264

stdweird opened this issue Mar 22, 2017 · 2 comments

Comments

@stdweird
Copy link
Member

stdweird commented Mar 22, 2017 •
edited by jrha
Loading

Currently in case of regular HTTPS, the aii-shellfe.conf certificate options are used for LWP (profiles.xml) and CCM::Fetch.
We also need to be able to pass the kerberos options to CCM / LWP.

Currently kerberised CDB is not supported.
@stdweird stdweird added this to the 17.4 milestone Mar 22, 2017
@stdweird stdweird modified the milestones: 17.10, 17.7 Jul 18, 2017
@jrha
Copy link
Member

jrha commented Nov 24, 2017

@stdweird are there other requirements driving this?
If not and it's just aspirational I'd rather it didn't have a milestone.

@stdweird
Copy link
Member Author

If you run freeipa with aii and you fetch the profiles remotely, this needs fixing. We (at ugent) don't require it (our AII server is our quattor server, and has the profiles locally; and we fetch them with dir:// magic).
Feel free to remove the milestone. I have no time to work on this (currently working on openstack and pacemaker...)

@jrha jrha modified the milestones: 17.12, 18.3 Nov 30, 2017
@jrha jrha removed this from the 18.3 milestone Mar 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jrha @stdweird