So what is the MaxTokenSize in SEAM, I just got a formula from MS on
what they use for 2003. Also we don't have this issue in SEAM for
Solaris 8 so what's different?
thanks,
Tyson Oswald
[EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]...
SEAM 1.01 doesn't support TCP, later version
MaxTokenSize is not a SEAM parameter. If the size of the token is too
large to fit in a single UDP datagram when PAC data is included, the KDC
switches to TCP.
I think Windows 2003 Server has a flag that can be set on the user
principals
to force it to stop putting PAC data in the
I'm currently working on the design of an authorisation system. For authentication,
making use of kerberos v5
seems the most suitable. I need the processes make authenticated RPC requests to a set
of authorisation and
capability broking servers. The problem I am having is that my 2 main specs
Does anyone know whether MIT's implementation can do concurrent
authentications for different users from different REALM/KDC?
Thanks,
- Ying
Kerberos mailing list [EMAIL PROTECTED]
https://mailman.mit.edu/mailman/listinfo/kerberos
Wyllys Ingersoll wrote:
MaxTokenSize is not a SEAM parameter. If the size of the token is too
large to fit in a single UDP datagram when PAC data is included, the KDC
switches to TCP.
I think Windows 2003 Server has a flag that can be set on the user
principals
to force it to stop
My basic objection to a load balancer is that Kerberos was designed to
do its own failover without one.
Kerberos was also originally designed to require FQDN's to uniquely map
to the destination IP numbers. Violations of those assumptions
deserved to fail because they might indicate some
