On 2017-04-27 14:00, Martin Bašti wrote:
>
>
> On 26.04.2017 20:41, Simo Sorce wrote:
>> On Wed, 2017-04-26 at 12:57 +0200, Martin Bašti wrote:
>>> On 25.04.2017 16:57, Martin Bašti wrote:
Hello all,
I'm going to implement automatic URI records for kdc proxy and I'd
like to
On 28.04.2017 09:32, Martin Kosek wrote:
On 04/27/2017 04:16 PM, Simo Sorce wrote:
On Thu, 2017-04-27 at 15:56 +0200, Petr Vobornik wrote:
On 04/27/2017 02:19 PM, Christian Heimes wrote:
On 2017-04-27 14:00, Martin Bašti wrote:
I would like to discuss consequences of adding kdc URI
On 04/27/2017 04:16 PM, Simo Sorce wrote:
> On Thu, 2017-04-27 at 15:56 +0200, Petr Vobornik wrote:
>> On 04/27/2017 02:19 PM, Christian Heimes wrote:
>>> On 2017-04-27 14:00, Martin Bašti wrote:
I would like to discuss consequences of adding kdc URI records:
1. basically all ipa
On 2017-04-27 16:16, Martin Bašti wrote:
>
>
> On 27.04.2017 14:19, Christian Heimes wrote:
>> On 2017-04-27 14:00, Martin Bašti wrote:
>>> I would like to discuss consequences of adding kdc URI records:
>>>
>>> 1. basically all ipa clients enrolled using autodiscovery will use
>>> kdcproxy
On Thu, 2017-04-27 at 15:56 +0200, Petr Vobornik wrote:
> On 04/27/2017 02:19 PM, Christian Heimes wrote:
> > On 2017-04-27 14:00, Martin Bašti wrote:
> > > I would like to discuss consequences of adding kdc URI records:
> > >
> > > 1. basically all ipa clients enrolled using autodiscovery will
>
On 27.04.2017 14:19, Christian Heimes wrote:
On 2017-04-27 14:00, Martin Bašti wrote:
I would like to discuss consequences of adding kdc URI records:
1. basically all ipa clients enrolled using autodiscovery will use
kdcproxy instead of KDC on port 88, because URI takes precedence over
SRV
On 04/27/2017 02:19 PM, Christian Heimes wrote:
On 2017-04-27 14:00, Martin Bašti wrote:
I would like to discuss consequences of adding kdc URI records:
1. basically all ipa clients enrolled using autodiscovery will use
kdcproxy instead of KDC on port 88, because URI takes precedence over
SRV
On 2017-04-27 14:00, Martin Bašti wrote:
> I would like to discuss consequences of adding kdc URI records:
>
> 1. basically all ipa clients enrolled using autodiscovery will use
> kdcproxy instead of KDC on port 88, because URI takes precedence over
> SRV in KRB5 client implementation. Are we ok
On 26.04.2017 20:41, Simo Sorce wrote:
On Wed, 2017-04-26 at 12:57 +0200, Martin Bašti wrote:
On 25.04.2017 16:57, Martin Bašti wrote:
Hello all,
I'm going to implement automatic URI records for kdc proxy and I'd
like to clarify if following URI records are the right one.
On Wed, 2017-04-26 at 12:57 +0200, Martin Bašti wrote:
>
> On 25.04.2017 16:57, Martin Bašti wrote:
> > Hello all,
> >
> > I'm going to implement automatic URI records for kdc proxy and I'd
> > like to clarify if following URI records are the right one.
> >
> >
> > _kerberos-adm.example.com. IN
On 25.04.2017 16:57, Martin Bašti wrote:
Hello all,
I'm going to implement automatic URI records for kdc proxy and I'd
like to clarify if following URI records are the right one.
_kerberos-adm.example.com. IN URI 0
"krb5srv:M:kkdcp:https://ipaserver.example.com/KdcProxy;
Hello all,
I'm going to implement automatic URI records for kdc proxy and I'd like
to clarify if following URI records are the right one.
_kerberos-adm.example.com. IN URI 0
"krb5srv:M:kkdcp:https://ipaserver.example.com/KdcProxy;
_krb5kdc.example.com. IN URI 0
12 matches
Mail list logo
