On 06/03/2014 09:07 AM, Johan Petersson wrote:
Hi,
Environment:
RHEL 7 IPA Server 3.3 with a trust to a Windows 2012 Server AD
RHEL 7 NFS Server
RHEL 7 Client
I have found one problem when using a NFS 4 shared Home Directory for
AD users logging in to IPA.
I have created a NFS share /hom
Hello again,
Just realised by re-reading this thread that I still needed to create
the DNA plugin.
I've now done that and I can add users, sorry for being stupid...
Dylan.
On 3 June 2014 14:44, Dylan Evans wrote:
> Hi Petr & Sumit,
>
> I've been trying to get further with my setup.
>
> 1. Th
Hi Petr & Sumit,
I've been trying to get further with my setup.
1. Thanks Petr, the groups.js plugin seems to work fine, it shows the
correct info on the GUI screen and seems to be ok.
2. Sumit, I'm afraid that I'm having a few more problems after running
" ipa-adtrust-install --add-sids". I can
Hi,
Environment:
RHEL 7 IPA Server 3.3 with a trust to a Windows 2012 Server AD
RHEL 7 NFS Server
RHEL 7 Client
I have found one problem when using a NFS 4 shared Home Directory for AD users
logging in to IPA.
I have created a NFS share /home/adexample.org and use autofs map in IPA.
All wbinfo
Kibana just renders the data, so I have no specific configuration for
that.
My logstash config (mostly cribbed from logstash.net) is as follows:
/etc/logstash/conf.d/syslog.conf
Containing:
input {
syslog {
type => syslog
port => 5544
}
udp {
type => syslogjson
port => 550
On Jun 3, 2014, at 4:37 AM, Innes, Duncan wrote:
> I'm starting to log IPA to a central point too. I'd hoped the A part of
> IPA would have arrived, but other functionality has pushed it down the
> priority list. Would be good to see it arrive as something integrated
> with systemd/journald wi
I'm starting to log IPA to a central point too. I'd hoped the A part of
IPA would have arrived, but other functionality has pushed it down the
priority list. Would be good to see it arrive as something integrated
with systemd/journald with fully separated log fields instead of a
simple log text l