ID-FF 1.2 Java ant deploy question

Discussion:

Chris Snyder

2005-06-13 20:15:58 UTC

Exactly the same thing I see. I have not generated SSL keys & certs because
I am running this in a closed lab, so I was relying on the demo keys. But, I
do get a whole bunch of servers running with JBoss:

TCP 0.0.0.0:4444 0.0.0.0:0 LISTENING
TCP 0.0.0.0:4445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8009 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8083 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8093 0.0.0.0:0 LISTENING

So I'm not sure what the issue is...

From: "Jack Lee" <***@hotmail.com>
To: ***@hotmail.com
Subject: RE: ID-FF 1.2 Java ant deploy question
Date: Mon, 13 Jun 2005 15:58:27 -0400

Hi Chris,

Thank you for your help.

I have once again come to another problem, and it appears I have to another
thread of yours once again. I have arrived to your thread called "ID-FF-2.0
Web does not start", citing an almost identical problem, where I tried to
start JBoss, and it halted at "Jk running ID=0 time=1/254 config=null". I
wonder if you have any ideas regarding this problem. Our instinct would be
SSL keys and certificates, would this be it? Or you have generated those
things already?

Please advise if you have any ideas.

Thanks.

Best Regards,

Jack Lee

Subject: RE: ID-FF 1.2 Java ant deploy question
Date: Fri, 10 Jun 2005 17:46:29 -0400
Hi Jack,
Yes I did fix it - six months later!
What I did: modify the build.properties file in EACH of the Castlepeak,
demo, and infrastructure directories. Don't just change the castlepeak file
and copy to the others... Then run "ant deploy" from the demo directory.
But I still have a problem: JBoss sees the id-ff services, but does not
start the webserver on port 8443. Still looking into that one.
Subject: ID-FF 1.2 Java ant deploy question
Date: Fri, 10 Jun 2005 15:22:12 -0400
Hi Chris,
I did a google search after facing the "ant deploy" problem, where "BUILD
FAILED" because the "${idff.dir} does not exist", similar to your post on
sourceid.org forum. I tried to follow the ensuing messages from your thread
and faced no luck. I was wondering at the end, how did you manage to fix
it, if you have.
Thanks!
Best Regards,
Jack Lee

David Waite

2005-06-13 20:50:57 UTC

Permalink

Did you perform step #4 in the supplied README (within the SAML
toolkit distribution)?

-David Waite

Post by Chris Snyder
Exactly the same thing I see. I have not generated SSL keys & certs
because I am running this in a closed lab, so I was relying on the
TCP 0.0.0.0:4444 0.0.0.0:0 LISTENING
TCP 0.0.0.0:4445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8009 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8083 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8093 0.0.0.0:0 LISTENING
So I'm not sure what the issue is...

David Waite
***@akuma.org

Chris Snyder

2005-06-14 17:55:50 UTC

Permalink

I didn't see a README file, but I followed the instructions in the user
guide (ID-FF 1.2 Java Toolkit 2.0 User's Guide).

Step four was:
4 After editing build.local.properties file, copy it to the Infrastructure
directory and the Demo directory.

But if I follow those instructions, ant deploy fails. Instead, I edited each
build.properties file. Are you suggesting that I create a
build.local.properties file within each demo directory?

Thanks.

From: David Waite <***@akuma.org>
Reply-To: SourceID Users List <sso-***@sourceid.org>
To: SourceID Users List <sso-***@sourceid.org>
CC: ***@hotmail.com
Subject: Re: [SourceID SSO-users] RE: ID-FF 1.2 Java ant deploy question
Date: Mon, 13 Jun 2005 14:50:57 -0600

Did you perform step #4 in the supplied README (within the SAML toolkit
distribution)?

-David Waite

Post by Chris Snyder
Exactly the same thing I see. I have not generated SSL keys & certs
because I am running this in a closed lab, so I was relying on the demo
TCP 0.0.0.0:4444 0.0.0.0:0 LISTENING
TCP 0.0.0.0:4445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8009 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8083 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8093 0.0.0.0:0 LISTENING
So I'm not sure what the issue is...

David Waite
***@akuma.org

David Waite

2005-06-14 20:27:42 UTC

Permalink

Within the README file included at the root of the SAML 1.1 Java
Toolkit 2.0 package, released as final last month:

4. Enable SSL in JBoss.
In ${jboss.server.dir}\deploy\jbossweb-tomcat50.sar\server.xml
un-comment the SSL connector and add/change the keystore and
truststore
parameters as follows:

<Connector port="8443" address="${jboss.bind.address}"
maxThreads="100" minSpareThreads="5" maxSpareThreads="15"
scheme="https" secure="true" clientAuth="false"
keystoreFile="${jboss.server.home.dir}/conf/sourceid.keystore"
keystorePass="changeit"
truststoreFile="${jboss.server.home.dir}/conf/
sourceid.keystore"
truststorePass="changeit"
sslProtocol="TLS"/>

Within the ID-FF 1.2 Java Toolkit 2.0 package, (final, released same
time): the equivalent file is in CastlePeak/README

-David Waite

Post by Chris Snyder
I didn't see a README file, but I followed the instructions in the
user guide (ID-FF 1.2 Java Toolkit 2.0 User's Guide).
4 After editing build.local.properties file, copy it to the
Infrastructure directory and the Demo directory.
But if I follow those instructions, ant deploy fails. Instead, I
edited each build.properties file. Are you suggesting that I create
a build.local.properties file within each demo directory?
Thanks.
Subject: Re: [SourceID SSO-users] RE: ID-FF 1.2 Java ant deploy question
Date: Mon, 13 Jun 2005 14:50:57 -0600
Did you perform step #4 in the supplied README (within the SAML
toolkit distribution)?
-David Waite

Post by Chris Snyder
Exactly the same thing I see. I have not generated SSL keys &
certs because I am running this in a closed lab, so I was relying
on the demo keys. But, I do get a whole bunch of servers running
TCP 0.0.0.0:4444 0.0.0.0:0 LISTENING
TCP 0.0.0.0:4445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8009 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8083 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8093 0.0.0.0:0 LISTENING
So I'm not sure what the issue is...

David Waite
_______________________________________________
sso-users mailing list
http://lists.sourceid.org/mailman/listinfo/sso-users
_______________________________________________
sso-users mailing list
http://lists.sourceid.org/mailman/listinfo/sso-users

David Waite
***@akuma.org

Chris Snyder

2005-06-14 21:09:34 UTC

Permalink

SUCCESS!!!!

I had missed the last close-comment in the xml...

BTW, my server.xml was located at:

C:\jboss\server\default\deploy\jbossweb-tomcat50.sar\

and I changed the SSL to:


<Connector port="8443" address="${jboss.bind.address}"
maxThreads="100" minSpareThreads="5" maxSpareThreads="15"
scheme="https" secure="true" clientAuth="false"
keystoreFile="${jboss.server.home.dir}/conf/sourceid.keystore"
keystorePass="changeit"
truststoreFile="${jboss.server.home.dir}/conf/sourceid.keystore"
truststorePass="changeit" sslProtocol = "TLS" />

Thank you!

From: David Waite <***@akuma.org>
Reply-To: SourceID Users List <sso-***@sourceid.org>
To: SourceID Users List <sso-***@sourceid.org>
Subject: Re: [SourceID SSO-users] RE: ID-FF 1.2 Java ant deploy question
Date: Tue, 14 Jun 2005 14:27:42 -0600

Within the README file included at the root of the SAML 1.1 Java Toolkit
2.0 package, released as final last month:

4. Enable SSL in JBoss.
In ${jboss.server.dir}\deploy\jbossweb-tomcat50.sar\server.xml
un-comment the SSL connector and add/change the keystore and truststore
parameters as follows:

<Connector port="8443" address="${jboss.bind.address}"
maxThreads="100" minSpareThreads="5" maxSpareThreads="15"
scheme="https" secure="true" clientAuth="false"
keystoreFile="${jboss.server.home.dir}/conf/sourceid.keystore"
keystorePass="changeit"
truststoreFile="${jboss.server.home.dir}/conf/ sourceid.keystore"
truststorePass="changeit"
sslProtocol="TLS"/>

Within the ID-FF 1.2 Java Toolkit 2.0 package, (final, released same time):
the equivalent file is in CastlePeak/README

-David Waite

I didn't see a README file, but I followed the instructions in the user
guide (ID-FF 1.2 Java Toolkit 2.0 User's Guide).
4 After editing build.local.properties file, copy it to the Infrastructure
directory and the Demo directory.
But if I follow those instructions, ant deploy fails. Instead, I edited
each build.properties file. Are you suggesting that I create a
build.local.properties file within each demo directory?
Thanks.
Subject: Re: [SourceID SSO-users] RE: ID-FF 1.2 Java ant deploy question
Date: Mon, 13 Jun 2005 14:50:57 -0600
Did you perform step #4 in the supplied README (within the SAML toolkit
distribution)?
-David Waite

Exactly the same thing I see. I have not generated SSL keys & certs
because I am running this in a closed lab, so I was relying on the demo
TCP 0.0.0.0:4444 0.0.0.0:0 LISTENING
TCP 0.0.0.0:4445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8009 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8083 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8093 0.0.0.0:0 LISTENING
So I'm not sure what the issue is...

David Waite
***@akuma.org

faysal mohammad

2005-06-15 13:42:05 UTC

Permalink

_______________________________________________
sso-users mailing list
sso-***@sourceid.org
http://lists.sourceid.org/mailman/listinfo/sso-users

Chris Snyder

2005-06-16 02:06:52 UTC

Permalink

I also get errors about clustering, but they don't seem to effect the
service. Takes about 50 seconds to load JBoss on a p3 866 with 1GB ram.

If you get the "Starting Coyote HTTP/1.1 on http-0.0.0.0-8443" message, then
the config is correct. If JBoss crashes soon after, then I would look at a
different version of JBoss or Java.

FYI my operating environment:
Win 2003 Server Ent
Sun Java SDK 1.4.2.08
Apache Ant 1.6.5
JBoss AS 3.2.4

From: "faysal mohammad" <***@hotmail.com>
To: sso-***@sourceid.org
CC: ***@hotmail.com, ***@akuma.org
Subject: Re: [SourceID SSO-users] RE: ID-FF 1.2 Java ant deploy question
Date: Wed, 15 Jun 2005 09:42:05 -0400

faysal mohammad

2005-06-14 18:20:57 UTC

Permalink

_______________________________________________
sso-users mailing list
sso-***@sourceid.org
http://lists.sourceid.org/mailman/listinfo/sso-users