RE: [docent_users] Re: Upgrading JVM for use with LiveConnect

Joe,

Yep, I thought about that too. It might still be an option.
Before I go down that path though, I want to look again at some kind of LDAP
piece since the customer already has LDAP in place.

Robert

From:
docent_users@yahoogroups.com [mailto:docent_users@yahoogroups.com] On Behalf
Of Joe Kyle
Sent: Tuesday, June 23, 2009 8:29 AM
To: docent_users@yahoogroups.com
Subject: [docent_users] Re: Upgrading JVM for use with LiveConnect

Hm. While it would be fairly inconvenient and
somewhat inefficient, one option that comes to mind is GatewayProgram. If you
can structure your flow and encapsulate both your authentication functionality
and the need to pass any data coming back from Active Directory in a single
call passed explicitly to a separate JVM 1.5+ installation, the performance
might not be so bad.

Unless you need to handle a high rate of logins/sec, it might be a reasonable
compromise against the effort required to regression-test (and then fix all the
version dependencies of) the rest of the Java code that's already there.

--
Joe Kyle
--jjkd--

--- In docent_users@yahoogroups.com,
"Robert Taylor" <robertt@...> wrote:
>
> Joe,
>
>
>
> Thanks. I knew I could count on you to always be in the loop on this.
>
>
>
> I was looking at JESPA for a transparent sign on integration.
> Unfortunately, it requires Java 1.5. I'm not able to use IIS security due
> to the domain structure, otherwise that would be the simplest way to do
> this.
>
>
>
> Thanks again.
>
>
>
> Robert
>
>
>
> From: docent_users@yahoogroups.com
[mailto:docent_users@yahoogroups.com]
On
> Behalf Of Joe Kyle
> Sent: Tuesday, June 23, 2009 6:05 AM
> To: docent_users@yahoogroups.com
> Subject: [docent_users] Re: Upgrading JVM for use with LiveConnect
>
>
>
>
>
>
>
>
> The only data point I can add is that in the recent required 'upgrade' of
> the Payflow Pro e-commerce integration, a direct like-for-like switch
would
> have required Java 1.5, and they didn't go that way. STS went to a fair
> amount of effort to switch APIs and added code to avoid Java 1.5
> requirements. Now, that's not really a new policy, so I'm not sure how
much
> this adds.
>
> Are you building something interesting/new that requires a newer version
of
> Java?
> --
> Joe Kyle
> --jjkd--
>
> --- In docent_users@yahoogroups.com
<mailto:docent_users%40yahoogroups.com>
> , "Robert Taylor" <robertt@> wrote:
> >
> > I know that we have talked in the past in about upgrading the Docent
JVM
> to
> > more recent versions and that this has failed in previous attempts.
Has
> > anyone managed to retry this successfully?
> >
> >
> >
> > Thank you.
> >
> >
> >
> > Robert Taylor
> >
>