--- Steve Jones <[EMAIL PROTECTED]> wrote:

> I can see no reasons for anyone to upgrade from 5.0 to 6.0, the only
> decent
> thing in 6.0 is that finally we managed to get Sun to start marking
> things
> for deletion in future releases (bye bye midi support) and 7.0 should
> support the concept of modules and profiles which is what is
> important.

Scripting is important... Particularly for operational automation. 
Jython support with WebLogic was one of happiest features from BEA's
customers.

One of the biggest pluses of Java SE 6 are the revisions to Kerberos
that finally make it
a) compatible with Active Directory's RC4-HMAC std. encryption
b) allow you to do outbound HTTP SPNEGO authentication with a KRB v5
ticket
c) don't force you to have to connect your app server to AD to get a
TGT 

I do hope the above is backported to Java SE 5, frankly.

Many, many customers of both SOAP services and HTTP web apps are
looking for single-sign on with Active Directory.   I've been involved
with many of these integrations, and it's not that hard once you've
spent a good couple of weeks toying with it & reading the specs.  But
Sun's implementation is woefully under-documented, IMO.   Much "folk
legend" abounds with such integration efforts.  

Further, I would say (c) has costed *millions* of dollars in
complaints, recrimination, and adult weeping.  And it's *not required*
by the Krb5 protocol, but for some reason Sun followed the GSS-API
recommendations to the letter and assumed anybody that 'accepts' a
credential will also 'initiate' later on.   Which is kinda tough when
you don't have SPNEGO outbound...  

Cheers
Stu



 
____________________________________________________________________________________
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.com

Reply via email to