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

Add How To Test HAProxy #3

Merged
merged 3 commits into from Jun 14, 2023
Merged

Add How To Test HAProxy #3

merged 3 commits into from Jun 14, 2023

Conversation

droideck
Copy link
Member

@droideck droideck commented Jun 9, 2023

No description provided.

## Introduction

A simple guide for HAProxy with LDAP configuration for testing purposes. If used in production, make sure to use valid certificates (as opposed to self-signed used in the guide).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As we may add other examples in the future,
I would add another chapter level:

Example supporting simple authentication over ldaps

Then

Step 1: Create Virtual Machines

...

I do not this it possible to perform GSSAPI or EXTERNAL (i.e certificate based) authentication over HAProxy with the current code but if someday it is possible, we want to document that in this howto.
And we may add the config on plain ldap (I wonder how the certificate validation for StartTLS would work through HAProxy - it probably does not work with current code ...)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vashirov may fix me, but HAProxy doesn't provide any easy and secure way for GSSAPI/EXTERNAL configuration if I understand correctly. It may forward what it gets from the client, but that's it.
And for StartTLS - the same's true.

We can have a task for future investigation, but I think we should go with SSL and recommend this to the 389 DS administrators.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'We can have a task for future investigation, but I think we should go with SSL and recommend this to the 389 DS administrators.'

Sorry if I was not clear. I fully agree with you, my point is only to:

  • structure the document in order to allow it to evolve if needed.
  • Precise clearly that this document describes the use of HAProxy over ldaps.
    It is an important point and it is not explicitly mentioned in the current version of the document.

FYI: About GSSAPI, I also do not think that there are any solutions, for EXTERNAL/StartTLS, IMHO there may be partial solution if NSS provides the right callbacks (but as you said, it is another story and another ticket !)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • structure the document in order to allow it to evolve if needed.
  • Precise clearly that this document describes the use of HAProxy over ldaps.
    It is an important point and it is not explicitly mentioned in the current version of the document.

Got it and fully agree! I'll restructure the doc accordingly...

@droideck
Copy link
Member Author

Okay, I clarified that the document is about LDAP/LDAPS and that a separate document will be created for GSSAPI/EXTERNAL and StartTLS (if it'll ever happens).

structure the document in order to allow it to evolve if needed.

I've tried to imagine how to restructure this document, but too many steps will be different if we include GSSAPI/EXTERNAL (starting from Step 2 and nearly to the final step). So I think it'll be better to create another doc and cross-link them between each other.
What do you think?

@droideck droideck requested a review from progier389 June 13, 2023 21:19
Copy link
Contributor

@progier389 progier389 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@droideck droideck merged commit ede1cdc into main Jun 14, 2023
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

Successfully merging this pull request may close these issues.

None yet

2 participants