search for: __after__

...RWDC. > > Can you please add to that bug report ? > > Rowland > > Thanks Rowland, that's exactly the topic. Garming Sam has commented it yesterday, the issue is that kerberos forwarding isn't implemented for now. That is exactly what wee seeing, authentication works __after__ (from the second attempt on) the initial password sync is done, the first attempt isn't proxied. Adam

...gt;> >>> Rowland >>> >>> >> >> Thanks Rowland, that's exactly the topic. Garming Sam has commented it >> yesterday, the issue is that kerberos forwarding isn't implemented for >> now. That is exactly what wee seeing, authentication works __after__ >> (from the second attempt on) the initial password sync is done, the >> first attempt isn't proxied. > > It should work, as long as you are using the internal Heimdal KDC, and > I thought we even had tests for that. The KDC propagates up a special > error code to the...

...; >>>>> >>>> >>>> Thanks Rowland, that's exactly the topic. Garming Sam has commented it >>>> yesterday, the issue is that kerberos forwarding isn't implemented for >>>> now. That is exactly what wee seeing, authentication works __after__ >>>> (from the second attempt on) the initial password sync is done, the >>>> first attempt isn't proxied. >>> >>> It should work, as long as you are using the internal Heimdal KDC, and >>> I thought we even had tests for that. The KDC propaga...

...hat bug report ? > > > > Rowland > > > > > > Thanks Rowland, that's exactly the topic. Garming Sam has commented it > yesterday, the issue is that kerberos forwarding isn't implemented for > now. That is exactly what wee seeing, authentication works __after__ > (from the second attempt on) the initial password sync is done, the > first attempt isn't proxied. It should work, as long as you are using the internal Heimdal KDC, and I thought we even had tests for that. The KDC propagates up a special error code to the processing layer to say &...

...t; > > > > > > > > > > > Thanks Rowland, that's exactly the topic. Garming Sam has commented it > > > yesterday, the issue is that kerberos forwarding isn't implemented for > > > now. That is exactly what wee seeing, authentication works __after__ > > > (from the second attempt on) the initial password sync is done, the > > > first attempt isn't proxied. > > > > It should work, as long as you are using the internal Heimdal KDC, and > > I thought we even had tests for that. The KDC propagates up a spe...

...t;> >>>>> >>>>> Thanks Rowland, that's exactly the topic. Garming Sam has commented it >>>>> yesterday, the issue is that kerberos forwarding isn't implemented for >>>>> now. That is exactly what wee seeing, authentication works __after__ >>>>> (from the second attempt on) the initial password sync is done, the >>>>> first attempt isn't proxied. >>>> >>>> It should work, as long as you are using the internal Heimdal KDC, and >>>> I thought we even had tests for th...

Hi, I've tried replacing some 2012R2 RODC by samba-4.9.4 RODCs. One question about password replication: Samba wiki (https://wiki.samba.org/index.php/Join_a_domain_as_a_RODC) states that samba RODC acts as a proxy server to a writable DC if users are not member of the Allowed RODC Password Replication Group, which is the behavior we knew (and what we want) from the MS RODCs. Our test

...> > > > > > Thanks Rowland, that's exactly the topic. Garming Sam has commented it > > > > > > yesterday, the issue is that kerberos forwarding isn't implemented for > > > > > > now. That is exactly what wee seeing, authentication works __after__ > > > > > > (from the second attempt on) the initial password sync is done, the > > > > > > first attempt isn't proxied. > > > > > > > > > > It should work, as long as you are using the internal Heimdal KDC, and > > > &...