Re: Kerberos Digest, Vol 211, Issue 5

Help

On Tue, 14 Jul 2020 at 5:52 AM, <[email protected]> wrote:

> Send Kerberos mailing list submissions to
>         [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://mailman.mit.edu/mailman/listinfo/kerberos
> or, via email, send a message with subject or body 'help' to
>         [email protected]
>
> You can reach the person managing the list at
>         [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Kerberos digest..."
>
>
> Today's Topics:
>
>    1. Kerberos Database Sync with Sub-Domains (Jonathan Towles)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 13 Jul 2020 18:58:39 +0000
> From: Jonathan Towles <[email protected]>
> Subject: Kerberos Database Sync with Sub-Domains
> To: "[email protected]" <[email protected]>
> Message-ID:
>         <
> MN2PR15MB3071B51D8434CF65FB80E728B9600@MN2PR15MB3071.namprd15.prod.outlook.com
> >
>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi All,
>
> I wanted to ask a question that I have been unable to get clear
> information on.
>
> Is it technically or functionally possible to get a Kerberos ticket for
> someone in the sub-domain against the parent domain
>
> Example:
>
> User [email protected]<mailto:[email protected]> wants to get
> a Kerberos ticket against dc01.synterex.com but will fail because that
> user is not found in the database on that Domain Controller.
>
> I didn't think that it was, but I wanted to check and see if anyone knows.
>
> Jon Towles
> CTO, Synterex
> (m) 978-609-5545
>
> [VMware Certified Professional - Digital Workspace 2020][VMware Certified
> Professional - Desktop and Mobility 2020][cid:[email protected]]
> [cid:[email protected]]  [cid:[email protected]]
> [cid:[email protected]]
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: image001.png
> Type: image/png
> Size: 6631 bytes
> Desc: image001.png
> Url :
> http://mailman.mit.edu/pipermail/kerberos/attachments/20200713/51c97692/attachment.png
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: image002.png
> Type: image/png
> Size: 6617 bytes
> Desc: image002.png
> Url :
> http://mailman.mit.edu/pipermail/kerberos/attachments/20200713/51c97692/attachment-0001.png
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: image003.jpg
> Type: image/jpeg
> Size: 3726 bytes
> Desc: image003.jpg
> Url :
> http://mailman.mit.edu/pipermail/kerberos/attachments/20200713/51c97692/attachment.jpg
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: image004.png
> Type: image/png
> Size: 8701 bytes
> Desc: image004.png
> Url :
> http://mailman.mit.edu/pipermail/kerberos/attachments/20200713/51c97692/attachment-0002.png
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: image005.png
> Type: image/png
> Size: 9055 bytes
> Desc: image005.png
> Url :
> http://mailman.mit.edu/pipermail/kerberos/attachments/20200713/51c97692/attachment-0003.png
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: image006.png
> Type: image/png
> Size: 14455 bytes
> Desc: image006.png
> Url :
> http://mailman.mit.edu/pipermail/kerberos/attachments/20200713/51c97692/attachment-0004.png
>
> ------------------------------
>
> _______________________________________________
> Kerberos mailing list
> [email protected]
> https://mailman.mit.edu/mailman/listinfo/kerberos
>
>
> End of Kerberos Digest, Vol 211, Issue 5
> ****************************************
>
________________________________________________
Kerberos mailing list           [email protected]
https://mailman.mit.edu/mailman/listinfo/kerberos