NextCloud with FreeIPA
-
Hi All,
I have NextCloud 12 and FreeIPA and i have a problem in the integration between NextCloud and FreeIPA,
i have followed what is stated in the NextCloud Documentation regarding this integration but the problem is that the NextCloud can not connect to LDAP Server,
i got the Error in the Logging of the NextCloud : " Configuration Error (prefix s01): login filter does not contain %uid place holder. "I have wrote the BaseDN as below :
dc=server,dc=local
UserDN as below :
uid=admin,cn=admins,dc=server,dc=local
Note :
i can test the connection normally using telnet utility for the FreeIPA using the port number " 389 " and connection is successfully initiated. -
Is there any advice ?
-
Sounds like FreeIPA does not have the format that NextCloud expects.
-
Someone else had this issue:
...I have already solved it. I had problem in firewall rule between DC (Domain controller) and Nextcloud server (I installed the certificate to /etc/openldap/certs from DC, or you may disable verification of certificate, just add "TLS_REQCERT never"). I had allowed only those ports (TCP 135, TCP 389, TPC 636, ICMP). So, l made firewall rule that allow all traffic (all TCP/UPD and ICMP) then I use "Detect Base DN". And it began to work ! I was able load groups, users etc... So the detection procedure using some high TCP ( > 1024). Then I went back default firewall rule and it still works.
-
@scottalanmiller said in NextCloud with FreeIPA:
Sounds like FreeIPA does not have the format that NextCloud expects.
it is supposed to be the same format of the OpenLDAP
-
the two systems are installed in docker and i have exposed all required ports , and there is no problem of any connection for any port
-
When you used telnet to test the connection, was that from the NextCloud host?
-
@scottalanmiller said in NextCloud with FreeIPA:
When you used telnet to test the connection, was that from the NextCloud host?
Yes , and it was connected on port 389
-
@AlyRagab said in NextCloud with FreeIPA:
@scottalanmiller said in NextCloud with FreeIPA:
When you used telnet to test the connection, was that from the NextCloud host?
Yes , and it was connected on port 389
Good old 389 Server, may it rest in piece. (Used to be RedHat's LDAP server for those that don't know.)
-
@travisdh1 said in NextCloud with FreeIPA:
@AlyRagab said in NextCloud with FreeIPA:
@scottalanmiller said in NextCloud with FreeIPA:
When you used telnet to test the connection, was that from the NextCloud host?
Yes , and it was connected on port 389
Good old 389 Server, may it rest in piece. (Used to be RedHat's LDAP server for those that don't know.)
You mean " Red Hat Identity Management " which includes " OpenLDAP 389 , Kerberos Authentication , NTP and DNS "
and the same with FreeIPA , it has all these components. -
@AlyRagab said in NextCloud with FreeIPA:
@travisdh1 said in NextCloud with FreeIPA:
@AlyRagab said in NextCloud with FreeIPA:
@scottalanmiller said in NextCloud with FreeIPA:
When you used telnet to test the connection, was that from the NextCloud host?
Yes , and it was connected on port 389
Good old 389 Server, may it rest in piece. (Used to be RedHat's LDAP server for those that don't know.)
You mean " Red Hat Identity Management " which includes " OpenLDAP 389 , Kerberos Authentication , NTP and DNS "
and the same with FreeIPA , it has all these components.I thought they had dropped the 389 name, huh.
-
Finally , i have solved the problem
this URL has made my day
NextCloud with FreeIPA -
@AlyRagab Hey, you have a new avatar.
-
@AlyRagab said in NextCloud with FreeIPA:
Finally , i have solved the problem
this URL has made my day
NextCloud with FreeIPAWell that is a really handy site.
-
@scottalanmiller Thanks a lot May you Categorize this thread so that it will be reference to anyone else
-
Done
