[
https://issues.apache.org/jira/browse/AIRFLOW-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Hansohn updated AIRFLOW-5613:
----------------------------------
Description:
Since Airflow is already using ldap3 for LDAP connections, I would like to
propose supporting multiple LDAP servers for failover purposes.
This change would be minimal and only be invoked when the {{uri}} param was
populated with a comma-separated string of LDAP servers.
The following would continue to use a ldap3
[Server|[https://ldap3.readthedocs.io/server.html]] object just as it does
today:
{code:java}
uri = ldaps://<your.ldap.server>:<port>
{code}
But when a comma-separated value was included a ldap3
[ServerPool|#server-pool]] object would be instantiated instead:
{code:java}
uri = ldaps://<your.ldap.server1>:<port>,ldaps://<your.ldap.server2>:<port>
{code}
I wanted to poll the community and see if this is something others might find
useful. I have a PR I am ready to submit to implement this change. Thoughts?
was:
Since Airflow is already using ldap3 for LDAP connections I would like to
propose supporting multiple LDAP servers for failover purposes.
This change would be minimal and only be invoked when the {{uri}} param was
populated with a comma-separated string of LDAP servers.
The following would continue to use a ldap3
[Server|[https://ldap3.readthedocs.io/server.html]] object just as it does
today:
{code:java}
uri = ldaps://<your.ldap.server>:<port>
{code}
But when a comma-separated value was included a ldap3
[ServerPool|[https://ldap3.readthedocs.io/server.html#server-pool]] object
would be instantiated instead:
{code:java}
uri = ldaps://<your.ldap.server1>:<port>,ldaps://<your.ldap.server2>:<port>
{code}
I wanted to poll the community and see if this is something others might find
useful. I have a PR I am ready to submit to implement this change. Thoughts?
> Suport multiple LDAP Servers
> ----------------------------
>
> Key: AIRFLOW-5613
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5613
> Project: Apache Airflow
> Issue Type: Improvement
> Components: authentication
> Affects Versions: 2.0.0
> Reporter: Ryan Hansohn
> Assignee: Ryan Hansohn
> Priority: Minor
>
> Since Airflow is already using ldap3 for LDAP connections, I would like to
> propose supporting multiple LDAP servers for failover purposes.
> This change would be minimal and only be invoked when the {{uri}} param was
> populated with a comma-separated string of LDAP servers.
> The following would continue to use a ldap3
> [Server|[https://ldap3.readthedocs.io/server.html]] object just as it does
> today:
> {code:java}
> uri = ldaps://<your.ldap.server>:<port>
> {code}
> But when a comma-separated value was included a ldap3
> [ServerPool|#server-pool]] object would be instantiated instead:
> {code:java}
> uri = ldaps://<your.ldap.server1>:<port>,ldaps://<your.ldap.server2>:<port>
> {code}
> I wanted to poll the community and see if this is something others might find
> useful. I have a PR I am ready to submit to implement this change. Thoughts?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
