Thanks @scottalanmiller
Posts made by AlyRagab
-
RE: NextCloud with FreeIPA
@scottalanmiller Thanks a lot May you Categorize this thread so that it will be reference to anyone else
-
RE: NextCloud with FreeIPA
Finally , i have solved the problem
this URL has made my day
NextCloud with FreeIPA -
RE: 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. -
RE: 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
-
RE: NextCloud with FreeIPA
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
-
RE: NextCloud with FreeIPA
@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
-
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. -
RE: Next Cloud Application
@scottalanmiller said in Next Cloud Application:
@AlyRagab said in Next Cloud Application:
@scottalanmiller said in Next Cloud Application:
@AlyRagab said in Next Cloud Application:
@scottalanmiller said in Next Cloud Application:
@AlyRagab said in Next Cloud Application:
@scottalanmiller it will be good , but this integration means that NextCloud can send mails from zimbra smtp connector ?
It can already do that. Currently Zimbra integrates into NextCloud. But in Zimbra 8.8 which releases soon, NextCloud integrates into Zimbra.
So we can integrate with the Zimbra LDAP with NextCloud
Right ?Yes. Zimbra uses OpenLDAP I believe. Or they can both talk to Active Directory.
Nice , this will make the login to the NextCloud as " [email protected] " and the same password of his mail account
Correct, that should work fine. I've not tried it, but no reason it should not work.
I will try with OpenLDAP " Mainly FreeIPA " then try with Zimbra
-
RE: Next Cloud Application
@scottalanmiller said in Next Cloud Application:
@AlyRagab said in Next Cloud Application:
@scottalanmiller said in Next Cloud Application:
@AlyRagab said in Next Cloud Application:
@scottalanmiller it will be good , but this integration means that NextCloud can send mails from zimbra smtp connector ?
It can already do that. Currently Zimbra integrates into NextCloud. But in Zimbra 8.8 which releases soon, NextCloud integrates into Zimbra.
So we can integrate with the Zimbra LDAP with NextCloud
Right ?Yes. Zimbra uses OpenLDAP I believe. Or they can both talk to Active Directory.
Nice , this will make the login to the NextCloud as " [email protected] " and the same password of his mail account
-
RE: Next Cloud Application
@scottalanmiller said in Next Cloud Application:
@AlyRagab said in Next Cloud Application:
@scottalanmiller it will be good , but this integration means that NextCloud can send mails from zimbra smtp connector ?
It can already do that. Currently Zimbra integrates into NextCloud. But in Zimbra 8.8 which releases soon, NextCloud integrates into Zimbra.
So we can integrate with the Zimbra LDAP with NextCloud
Right ? -
RE: Next Cloud Application
@scottalanmiller it will be good , but this integration means that NextCloud can send mails from zimbra smtp connector ?
-
RE: Next Cloud Application
@dafyre said in Next Cloud Application:
@AlyRagab said in Next Cloud Application:
It is great Application and here are the Features
https://nextcloud.com/features/There's a lot of nextCloud users here! If you have questions, feel free to ask.
I am planing to integrate it with OpenLDAP , if i have any issue on it will post it here , this is my favorite IT Forum
-
Next Cloud Application
It is great Application and here are the Features
https://nextcloud.com/features/ -
RE: CLVM for CentOS 7
@AlyRagab and from the storage side :
# targetcli sessions alias: node1.server.local sid: 4 type: Normal session-state: LOGGED_IN alias: node2.server.local sid: 5 type: Normal session-state: LOGGED_IN alias: node3.server.local sid: 2 type: Normal session-state: LOGGED_IN
-
RE: CLVM for CentOS 7
@travisdh1 said in CLVM for CentOS 7:
@AlyRagab That's looking like something is wrong with the iSCSI mount.
i am using the below commands to access the storage :
the IP Address of the Target is : 192.168.1.40iscsiadm -m discovery -t sendtargets -p 192.168.1.40 iscsiadm -m node -T iqn.2017-05.local.server:target -p 192.168.1.40:3260 --login
-
RE: CLVM for CentOS 7
pvdisplay command output too
[root@node1 ~]# pvdisplay
connect() failed on local socket: No such file or directory
Internal cluster locking initialisation failed.
WARNING: Falling back to local file-based locking.
Volume Groups with the clustered attribute will be inaccessible.
--- Physical volume ---
PV Name /dev/sda2
VG Name centos
PV Size 29.51 GiB / not usable 3.00 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 7554
Free PE 11
Allocated PE 7543
PV UUID kI6RJ1-ZfLZ-vSNW-teO3-dheF-aK8j-OKSole"/dev/sdb1" is a new physical volume of "60.00 GiB"
--- NEW Physical volume ---
PV Name /dev/sdb1
VG Name
PV Size 60.00 GiB
Allocatable NO
PE Size 0
Total PE 0
Free PE 0
Allocated PE 0
PV UUID P1CkZw-jq49-a6T6-mwO5-EQtz-y4dX-BYcUWq -
RE: CLVM for CentOS 7
@travisdh1 said in CLVM for CentOS 7:
@AlyRagab said in CLVM for CentOS 7:
@scottalanmiller sorry , i mean i want to create the volume group based on this pyhiscal partition using the CLVM but i can not at this moment to do that
What does
pvdisplay
currently list?here is the output of the pvs command
[root@node1 ~]# pvs
connect() failed on local socket: No such file or directory
Internal cluster locking initialisation failed.
WARNING: Falling back to local file-based locking.
Volume Groups with the clustered attribute will be inaccessible.
PV VG Fmt Attr PSize PFree
/dev/sda2 centos lvm2 a-- 29.51g 44.00m
/dev/sdb1 lvm2 --- 60.00g 60.00g