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

[dev.icinga.com #11809] Test and document multiple LDAP-URIs separated by space in LDAP ressources #2430

Closed
icinga-migration opened this issue May 18, 2016 · 7 comments
Labels
area/authentication Affects user authentication or authorization enhancement New feature or improvement
Milestone

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/11809

Created by schinken on 2016-05-18 13:47:58 +00:00

Assignee: (none)
Status: Resolved (closed on 2016-12-12 15:44:42 +00:00)
Target Version: 2.4.0
Last Update: 2016-12-12 15:44:42 +00:00 (in Redmine)


In my opinion, it should be possible to assign a secondary ldap server. Maybe as a comma separated value in the hostname field, or with multiple definitions of a ldap resource

Changesets

2016-12-12 15:42:56 +00:00 by elippmann de94749

Note that its possible to provide multiple LDAP hosts separated by a space

fixes #11809

Relations:

@icinga-migration
Copy link
Author

Updated by elippmann on 2016-05-24 07:41:09 +00:00

  • Tracker changed from Feature to Support
  • Status changed from New to Feedback
  • Assigned to set to schinken

Hi,

It's possible to use more than one LDAP servers for authentication. You may either use the domain as the host name in your configuration or you may define two authentication w/ two separate resources. Does this help?

Best regards,
Eric

@icinga-migration
Copy link
Author

Updated by schinken on 2016-06-09 07:56:53 +00:00

Ah okay. I think that'll do it.

Thank you

@icinga-migration
Copy link
Author

Updated by ClemensBW on 2016-06-30 09:33:46 +00:00

Hello,

can you please mark this as feature request? I'll like to have a "backup" LDAP server, if the first ist not reachable. Not a manuell switchover.

@icinga-migration
Copy link
Author

Updated by darmagan on 2016-07-12 15:16:37 +00:00

Hello,

info:
it's also possible to list the hostnames seperated by white spaces:

[auth_ad]
type = "ldap"
hostname = "ldaps://server123.domain.com ldaps://server987.domain.com"
port = "636"
root_dn = "DCXXXXXcom"
bind_dn = "XXXcom"
bind_pw = "XXX"

regards

@icinga-migration
Copy link
Author

Updated by elippmann on 2016-07-14 07:45:05 +00:00

  • Tracker changed from Support to Feature
  • Subject changed from Secondary LDAP-Server to Test and document multiple LDAP-URIs separated by space in LDAP ressources
  • Status changed from Feedback to New
  • Assigned to deleted schinken
  • Target Version set to 2.4.0

@icinga-migration
Copy link
Author

Updated by elippmann on 2016-12-12 15:44:42 +00:00

  • Status changed from New to Resolved
  • Done % changed from 0 to 100

Applied in changeset de94749.

@icinga-migration
Copy link
Author

Updated by mfrosch on 2016-12-13 12:54:00 +00:00

  • Relates set to 13539

@icinga-migration icinga-migration added enhancement New feature or improvement area/authentication Affects user authentication or authorization labels Jan 17, 2017
@icinga-migration icinga-migration added this to the 2.4.0 milestone Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/authentication Affects user authentication or authorization enhancement New feature or improvement
Projects
None yet
Development

No branches or pull requests

1 participant