[Freeipa-users] Re: Kvno error on validating one-way trust: "kvno: Decrypt integrity check failed while getting credentials"

2017-09-06 Thread Alexander Bokovoy via FreeIPA-users
On ke, 06 syys 2017, Bart J via FreeIPA-users wrote: Thank you. I checked in my test environment and setting trust with administrative credentials works. I got mixed results for Windows 2012 and Windows 2008 R2 because I previously had set up trust using administrative credentials for Windows

[Freeipa-users] Re: Kvno error on validating one-way trust: "kvno: Decrypt integrity check failed while getting credentials"

2017-09-06 Thread Bart J via FreeIPA-users
Thank you. I checked in my test environment and setting trust with administrative credentials works. I got mixed results for Windows 2012 and Windows 2008 R2 because I previously had set up trust using administrative credentials for Windows 2012. Later, even though I deleted it on FreeIPA's

[Freeipa-users] Re: Kvno error on validating one-way trust: "kvno: Decrypt integrity check failed while getting credentials"

2017-08-30 Thread Alexander Bokovoy via FreeIPA-users
On ti, 22 elo 2017, bogusmaster--- via FreeIPA-users wrote: Hi All, I am setting up a one-way trust from FreeIPA server to AD domain with a pre-shared key. This is currently not working due to chicken/egg problem: in order to turn trust into an active one, you need to validate it. We do not

[Freeipa-users] Re: Kvno error on validating one-way trust: "kvno: Decrypt integrity check failed while getting credentials"

2017-08-30 Thread Sumit Bose via FreeIPA-users
On Wed, Aug 30, 2017 at 10:45:11AM -, bogusmaster--- via FreeIPA-users wrote: > Behavior that I described above pertains to Windows 2008 R2. When I attempt > at doing exactly the same with AD set up on top of Windows 2012, it works > flawlessly. Unfortunately, environment I have to set up

[Freeipa-users] Re: Kvno error on validating one-way trust: "kvno: Decrypt integrity check failed while getting credentials"

2017-08-30 Thread bogusmaster--- via FreeIPA-users
Behavior that I described above pertains to Windows 2008 R2. When I attempt at doing exactly the same with AD set up on top of Windows 2012, it works flawlessly. Unfortunately, environment I have to set up trust with uses Windows 2008 R2. I am wondering what might be the difference between