Hello Sergei,
I've looked around, and If you really want to use OpenSSO, you can  build the 
jars from the source. 
The source code is available:
https://opensso.dev.java.net/source/browse/opensso/
and the libraries for building jars from source is also available:
https://opensso.dev.java.net/public/use/index.html
OpenSSO External Library Bundle

Thanks,
-----Original Message-----
From: Nick Hauenstein [mailto:ni...@quicklearn.com] 
Sent: Thursday, December 02, 2010 3:57 PM
To: stonehenge-dev@incubator.apache.org
Subject: RE: Error building java trader_client

IIRC (and I might not, since I'm no Java expert) OpenSSO was only being used 
for the Passive STS, and there was a custom metro Active STS. If that is 
correct, to get the trader client working sans OpenSSO, you would need to 
configure it to use the .NET Passive STS, or the WSAS Passive STS. I haven't 
been able to find specific emails discussing those scenarios (because the mail 
volume is so large, and the keywords I would search so frequently occurring), 
but I am certain that the trader_client would not have been removed if we could 
either (a) show those scenarios working and/or (b) divorce the metro 
trader_client entirely from its OpenSSO dependency.

I was looking at a slide deck from a presentation on Stonehenge (shortly before 
the release of M2), and the known good compatibility was as follows:

        .NET Passive STS -> Metro Active STS
        .NET Web App -> Metro Active STS
        .NET Web App -> Metro Business Service
        .NET Business Service -> Metro Order Processor
        .NET Business Service -> WSAS Order Processor
        .NET Business Service -> .NET Order Processor
        WSAS Passive STS -> .NET Web App
        WSAS Business Service -> Metro Order Processor
        WSAS Business Service -> .NET Order Processor
        WSAS Business Service -> WSAS Order Processor

So the project did demonstrate interoperability, but also found some 
incompatibilities that were not yet overcome.

- Nick Hauenstein


-----Original Message-----
From: Akopov, Sergei (GE Intelligent Platforms) [mailto:sergei.ako...@ge.com]
Sent: Thursday, December 02, 2010 3:00 PM
To: stonehenge-dev@incubator.apache.org
Subject: RE: Error building java trader_client

Is it required to have OpenSSO setup to make metro trader-client to talk to 
metro service, at least? 
I am a bit confused, maybe I am asking the wrong questions but I thought this 
was a project on interoperability. Is Microsoft still involved in this project?

Serge.

-----Original Message-----
From: Nick Hauenstein [mailto:ni...@quicklearn.com]
Sent: Thursday, December 02, 2010 4:12 PM
To: stonehenge-dev@incubator.apache.org
Subject: RE: Error building java trader_client

I don't think that release ever made it out (due to the Sun/Oracle merger). 
Another company forked OpenSSO, and released it under the name OpenAM. OpenAM 
Snapshot 9 [1] *should* be the equivalent of OpenSSO 9 Express, but don't hold 
me to it.

We were all using a random nightly build that disappeared one day.

- Nick Hauenstein

[1]
https://wikis.forgerock.org/confluence/display/openam/OpenAM+Snapshot+9+
Release+Notes

-----Original Message-----
From: Akopov, Sergei (GE Intelligent Platforms) [mailto:sergei.ako...@ge.com]
Sent: Thursday, December 02, 2010 12:57 PM
To: stonehenge-dev@incubator.apache.org
Subject: RE: Error building java trader_client

Nick,

The install list includes OpenSSO 9 Express deployment. I cannot find the zip 
file on the web, does anyone have it?

Thanks,
Serge.

Reply via email to