I've found what was wrong. Keycloak process must be run with FreeIPA user
-- admin as it is by the documentation.
I guess documentation lacks to note this, or alert this is the case.
Found this by reading
https://dbus.freedesktop.org/doc/dbus-specification.html
Kind regards,
Miroslav
V V ned., 18. avg. 2019 ob 07:43 je oseba Miroslav Beranič <
miroslav.beranic(a)mibesis.si> napisala:
Hi all,
I have same problems as described in an existing JIRA:
https://issues.jboss.org/browse/KEYCLOAK-8095
I have followed suggested documentation located at:
https://www.keycloak.org/docs/latest/server_admin/index.html#_sssd
With differences:
- I do not use docker - using standalone computer node
- I use DNS, so I did not update /etc/hosts file
- I run as root user ( I've tried both - with dedicated user also, same
result )
( in file /etc/sssd/sssd.conf I have :
[ifp]
allowed_uids = root
)
[root@sso keycloak-8.0.0-SNAPSHOT]# sssctl user-checks admin -s keycloak
user: admin
action: acct
service: keycloak
SSSD nss user lookup result:
- user name: admin
- user id: 804200000
- group id: 804200000
- gecos: Administrator
- home directory: /home/admin
- shell: /bin/bash
SSSD InfoPipe user lookup result:
- name: admin
- uidNumber: 804200000
- gidNumber: 804200000
- gecos: Administrator
- homeDirectory: /home/admin
- loginShell: /bin/bash
- sn: Administrator
testing pam_acct_mgmt
pam_acct_mgmt: Success
PAM Environment:
- no env -
Is there any additional validation test I can run, to validate server
setup?
Kind Regards,
Miroslav
--
Miroslav Beranič
MIBESIS
miroslav.beranic(a)mibesis.si
https://www.mibesis.si
--
Miroslav Beranič
MIBESIS
miroslav.beranic(a)mibesis.si
https://www.mibesis.si