ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    FreeIPA Server & Client

    Scheduled Pinned Locked Moved IT Discussion
    47 Posts 4 Posters 6.7k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • stacksofplatesS
      stacksofplates
      last edited by

      Do you have an OTP set up for that user?

      1 Reply Last reply Reply Quote 0
      • stacksofplatesS
        stacksofplates
        last edited by

        Also, can you SSH in as the IPA user, without using su?

        AlyRagabA 2 Replies Last reply Reply Quote 0
        • AlyRagabA
          AlyRagab @stacksofplates
          last edited by

          @stacksofplates i can not login as ssh using the IPA user , after writing the password it gives this error :
          Permission denied, please try again

          1 Reply Last reply Reply Quote 0
          • AlyRagabA
            AlyRagab @stacksofplates
            last edited by

            @stacksofplates also there is no any OTP Configuration on the IPA Server

            1 Reply Last reply Reply Quote 0
            • stacksofplatesS
              stacksofplates
              last edited by

              Can you post your /etc/pam.d/system-auth and password-auth configs?

              AlyRagabA 1 Reply Last reply Reply Quote 0
              • AlyRagabA
                AlyRagab @stacksofplates
                last edited by

                @stacksofplates the " /etc/pam.d/system-auth "

                #%PAM-1.0

                This file is auto-generated.

                User changes will be destroyed the next time authconfig is run.

                auth required pam_env.so
                auth sufficient pam_fprintd.so
                auth sufficient pam_unix.so nullok try_first_pass
                auth requisite pam_succeed_if.so uid >= 1000 quiet_success
                auth sufficient pam_sss.so use_first_pass
                auth required pam_deny.so

                account required pam_unix.so
                account sufficient pam_localuser.so
                account sufficient pam_succeed_if.so uid < 1000 quiet
                account [default=bad success=ok user_unknown=ignore] pam_sss.so
                account required pam_permit.so

                password requisite pam_pwquality.so try_first_pass local_users_only retry=3 authtok_type=
                password sufficient pam_unix.so sha512 shadow nullok try_first_pass use_authtok
                password sufficient pam_sss.so use_authtok
                password required pam_deny.so

                session optional pam_keyinit.so revoke
                session required pam_limits.so
                -session optional pam_systemd.so
                session optional pam_oddjob_mkhomedir.so umask=0077
                session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid
                session required pam_unix.so
                session optional pam_sss.so

                =================================================

                and " /etc/pam.d/password-auth "

                #%PAM-1.0

                This file is auto-generated.

                User changes will be destroyed the next time authconfig is run.

                auth required pam_env.so
                auth sufficient pam_unix.so nullok try_first_pass
                auth requisite pam_succeed_if.so uid >= 1000 quiet_success
                auth sufficient pam_sss.so use_first_pass
                auth required pam_deny.so

                account required pam_unix.so
                account sufficient pam_localuser.so
                account sufficient pam_succeed_if.so uid < 1000 quiet
                account [default=bad success=ok user_unknown=ignore] pam_sss.so
                account required pam_permit.so

                password requisite pam_pwquality.so try_first_pass local_users_only retry=3 authtok_type=
                password sufficient pam_unix.so sha512 shadow nullok try_first_pass use_authtok
                password sufficient pam_sss.so use_authtok
                password required pam_deny.so

                session optional pam_keyinit.so revoke
                session required pam_limits.so
                -session optional pam_systemd.so
                session optional pam_oddjob_mkhomedir.so umask=0077
                session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid
                session required pam_unix.so
                session optional pam_sss.so

                1 Reply Last reply Reply Quote 0
                • stacksofplatesS
                  stacksofplates
                  last edited by

                  Looks fairly normal. What's in your /etc/nsswitch.conf file?

                  1 Reply Last reply Reply Quote 0
                  • stacksofplatesS
                    stacksofplates
                    last edited by

                    Also, if you log into the system with a different user, can you do a kinit ldapuser to get a kerberos ticket?

                    AlyRagabA 1 Reply Last reply Reply Quote 1
                    • AlyRagabA
                      AlyRagab @stacksofplates
                      last edited by

                      @stacksofplates the " /etc/nsswitch.conf "

                      passwd: files sss
                      shadow: files sss
                      group: files sss
                      #initgroups: files

                      #hosts: db files nisplus nis dns
                      hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname

                      Example - obey only what nisplus tells us...

                      #services: nisplus [NOTFOUND=return] files
                      #networks: nisplus [NOTFOUND=return] files
                      #protocols: nisplus [NOTFOUND=return] files
                      #rpc: nisplus [NOTFOUND=return] files
                      #ethers: nisplus [NOTFOUND=return] files
                      #netmasks: nisplus [NOTFOUND=return] files

                      bootparams: nisplus [NOTFOUND=return] files

                      ethers: files
                      netmasks: files
                      networks: files
                      protocols: files
                      rpc: files
                      services: files sss

                      netgroup: files sss

                      publickey: nisplus

                      automount: files sss
                      aliases: files nisplus
                      sudoers: files sss

                      ==============
                      also what make the case is very strange is that i can do kinit ldapuser normally and su - user
                      also getent passwd user
                      but can not login as ssh or GUI

                      1 Reply Last reply Reply Quote 0
                      • AlyRagabA
                        AlyRagab
                        last edited by

                        i think the main question here is : how can we allow the Enterprise Login ?

                        1 Reply Last reply Reply Quote 0
                        • stacksofplatesS
                          stacksofplates
                          last edited by

                          Did you change the password for the user after you set it?

                          Can you log into the IPA web interface with that user?

                          AlyRagabA 1 Reply Last reply Reply Quote 0
                          • AlyRagabA
                            AlyRagab @stacksofplates
                            last edited by

                            @stacksofplates said in FreeIPA Server & Client:

                            Did you change the password for the user after you set it?

                            Can you log into the IPA web interface with that user?

                            the password is changed in the first login
                            and also i can access the IPA web interface with that user

                            1 Reply Last reply Reply Quote 0
                            • stacksofplatesS
                              stacksofplates
                              last edited by

                              It really sounds like it's something to do with pam. You can try doing an authconfig --update and see if that helps. If not, I'd just reinstall the ipa-client.

                              1 Reply Last reply Reply Quote 1
                              • stacksofplatesS
                                stacksofplates
                                last edited by

                                Another thing to try, do you have the ipa-admintools package installed on your client? If you do, what output do you get if you kinit and then run ipa user-find --all?

                                AlyRagabA 1 Reply Last reply Reply Quote 0
                                • stacksofplatesS
                                  stacksofplates
                                  last edited by

                                  This post is deleted!
                                  1 Reply Last reply Reply Quote 0
                                  • stacksofplatesS
                                    stacksofplates
                                    last edited by

                                    This post is deleted!
                                    1 Reply Last reply Reply Quote 0
                                    • AlyRagabA
                                      AlyRagab @stacksofplates
                                      last edited by

                                      @stacksofplates said in FreeIPA Server & Client:

                                      Another thing to try, do you have the ipa-admintools package installed on your client? If you do, what output do you get if you kinit and then run ipa user-find --all?

                                      the admintools package is installed , but when i tried to run " ipa user-find --all " it shows this error :
                                      [root@client ~]# ipa user-find --all
                                      ipa: ERROR: 2.114 client incompatible with 2.112 server at 'https://ipa.server.local/ipa/xml'

                                      stacksofplatesS 1 Reply Last reply Reply Quote 0
                                      • stacksofplatesS
                                        stacksofplates @AlyRagab
                                        last edited by stacksofplates

                                        @AlyRagab said in FreeIPA Server & Client:

                                        @stacksofplates said in FreeIPA Server & Client:

                                        Another thing to try, do you have the ipa-admintools package installed on your client? If you do, what output do you get if you kinit and then run ipa user-find --all?

                                        the admintools package is installed , but when i tried to run " ipa user-find --all " it shows this error :
                                        [root@client ~]# ipa user-find --all
                                        ipa: ERROR: 2.114 client incompatible with 2.112 server at 'https://ipa.server.local/ipa/xml'

                                        That's what I feared. I think to be able to run the IPA client on Fedora you will need to run the IPA server on Fedora server, not CentOS.

                                        Or go the opposite and use CentOS 7 workstation instead of Fedora. I actually prefer the CentOS 7 workstation to Fedora, and I'm going to be switching back on my home laptop.

                                        scottalanmillerS 1 Reply Last reply Reply Quote 0
                                        • scottalanmillerS
                                          scottalanmiller @stacksofplates
                                          last edited by

                                          @stacksofplates said in FreeIPA Server & Client:

                                          @AlyRagab said in FreeIPA Server & Client:

                                          @stacksofplates said in FreeIPA Server & Client:

                                          Another thing to try, do you have the ipa-admintools package installed on your client? If you do, what output do you get if you kinit and then run ipa user-find --all?

                                          the admintools package is installed , but when i tried to run " ipa user-find --all " it shows this error :
                                          [root@client ~]# ipa user-find --all
                                          ipa: ERROR: 2.114 client incompatible with 2.112 server at 'https://ipa.server.local/ipa/xml'

                                          That's what I feared. I think to be able to run the IPA client on Fedora you will need to run the IPA server on Fedora server, not CentOS.

                                          Or go the opposite and use CentOS 7 workstation instead of Fedora. I actually prefer the CentOS 7 workstation to Fedora, and I'm going to be switching back on my home laptop.

                                          What about CentOS 7 workstation are you liking? I'm a Fedora fan and like Korora's mix of it the most.

                                          stacksofplatesS 1 Reply Last reply Reply Quote 0
                                          • stacksofplatesS
                                            stacksofplates @scottalanmiller
                                            last edited by stacksofplates

                                            @scottalanmiller said in FreeIPA Server & Client:

                                            @stacksofplates said in FreeIPA Server & Client:

                                            @AlyRagab said in FreeIPA Server & Client:

                                            @stacksofplates said in FreeIPA Server & Client:

                                            Another thing to try, do you have the ipa-admintools package installed on your client? If you do, what output do you get if you kinit and then run ipa user-find --all?

                                            the admintools package is installed , but when i tried to run " ipa user-find --all " it shows this error :
                                            [root@client ~]# ipa user-find --all
                                            ipa: ERROR: 2.114 client incompatible with 2.112 server at 'https://ipa.server.local/ipa/xml'

                                            That's what I feared. I think to be able to run the IPA client on Fedora you will need to run the IPA server on Fedora server, not CentOS.

                                            Or go the opposite and use CentOS 7 workstation instead of Fedora. I actually prefer the CentOS 7 workstation to Fedora, and I'm going to be switching back on my home laptop.

                                            What about CentOS 7 workstation are you liking? I'm a Fedora fan and like Korora's mix of it the most.It

                                            I like fedora a lot. But I had CentOS workstation for a long time after 7 came out. It's rock solid, like you have to try to break it. I've had some weird issues with fedora, both 23 and 24 that seemed a little buggy. In my experience Fedora with Gnome has been slower than CentOS with Gnome. Ive only ever found one thing I couldn't run on CentOS and that was FreeCAD, but it didn't run super well on Fedora either.

                                            Plus there is the not needing to reinstall every 6 months or whatever the release schedule is.

                                            And the fact I work with RHEL 7 WS every day, it feels comfortable.

                                            scottalanmillerS 1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 3 / 3
                                            • First post
                                              Last post