As far as I know, the keys are okay.  I recently ran through all of the test
cases in Bamboo and it succeeded.  I've run them on both a Windows and a
Solaris machine.

Unless something got messed up when they were archived.  Have you tried the
version in Subversion?

-Scott

On 6/21/07, Philip Brusten <[EMAIL PROTECTED]> wrote:

Don't know about any export rules :o)

This is the output of
TEST-org.jasig.cas.authentication.principal.GoogleAccountsServiceTests.xml

  <testcase time="0.015" name="testResponse">
    <error type="java.security.spec.InvalidKeySpecException"
message="Inappropriate key specification: IOException: algid parse
error, not a sequence">java.security.spec.Invalid
KeySpecException: Inappropriate key specification: IOException: algid
parse error, not a sequence
        at
sun.security.provider.DSAKeyFactory.engineGeneratePublic(
DSAKeyFactory.java:104)
        at java.security.KeyFactory.generatePublic(KeyFactory.java:284)
        at
org.jasig.cas.util.PublicKeyFactoryBean.createInstance(
PublicKeyFactoryBean.java:39)
        at

org.springframework.beans.factory.config.AbstractFactoryBean.afterPropertiesSet
(AbstractFactoryBean.java:120)
        at

org.jasig.cas.authentication.principal.GoogleAccountsServiceTests.getGoogleAccountsService
(GoogleAccountsServiceTests.java:46)
        at
org.jasig.cas.authentication.principal.GoogleAccountsServiceTests.setUp(
GoogleAccountsServiceTests.java:61)
        at junit.framework.TestCase.runBare(TestCase.java:125)
        at junit.framework.TestResult$1.protect(TestResult.java:106)
        at junit.framework.TestResult.runProtected(TestResult.java:124)
        at junit.framework.TestResult.run(TestResult.java:109)
        at junit.framework.TestCase.run(TestCase.java:118)
        at junit.framework.TestSuite.runTest(TestSuite.java:208)
        at junit.framework.TestSuite.run(TestSuite.java:203)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at
org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java
:213)
        at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(
AbstractDirectoryTestSuite.java:138)
        at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(
AbstractDirectoryTestSuite.java:125)
        at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(
SurefireBooter.java:290)
        at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java
:818)
        at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java
:818)
</error>
  </testcase>


Apparently there's a problem with the DSA keys that are loaded by the
test class. Some searching on Google pointed me to the following URL:
http://forum.java.sun.com/thread.jspa?threadID=270930&messageID=1037530

The keys reside at
cas-server-3.1-rc2/cas-server-core/src/test/resources/DSAPublicKey01.key
cas-server-3.1-rc2/cas-server-core/src/test/resources/DSAPrivateKey01.key
cas-server-3.1-rc2/cas-server-core/target/test-classes/DSAPublicKey01.key
cas-server-3.1-rc2/cas-server-core/target/test-classes/DSAPrivateKey01.key

Is there a problem with the format of the keys?

Philip




Scott Battaglia wrote:
> Are there any export rules for XML Security with regards to other
countries?
>
> Also, in cas-server-core/target/surefire-reports/ there should be a file
> for that class with more specific exception information.  I'm just
> guessing its the same error I was having before.
>
> -Scott
>
> On 6/21/07, *Philip Brusten* <[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>> wrote:
>
>     I'm using the official java distribution of debian: sun-java5-jdk
>                               1.5.0-10-3
>
>     I also tried the jdk1.5.0_12 under windows, resulting in the same
>     error...
>
>     Philip
>
>
>
>     Scott Battaglia wrote:
>     > Which version of the JVM are you using?  Apparently older versions
of
>     > the Java 1.5 JVM don't include the XML Security needed for the JSR
105
>     > support (I've had success with Java 1.5.0_11 and Java 6).
>     >
>     > If anyone knows how to switch JSR 105 providers so we are not
>     dependent
>     > on the JVM version, please let me know. (btw, we're only dependent
>     on it
>     > for the Google Accounts support and nothing else).
>     >
>     > -Scott
>     >
>     > On 6/21/07, *Philip Brusten* <[EMAIL PROTECTED]
>     <mailto:[EMAIL PROTECTED]>
>     > <mailto:[EMAIL PROTECTED]
>     <mailto:[EMAIL PROTECTED]>>> wrote:
>     >
>     >     Scott Battaglia wrote:
>     >     > Yes, there were two places it needed to be changed.  Only
>     one of them
>     >     > had been changed.  It *should* be fixed when RC3 comes out
>     (along
>     >     with a
>     >     > couple of other things).
>     >
>     >     I changed "cas-server-support-spnego" to
>     "cas-server-support-windows" in
>     >     pom.xml.
>     >
>     >     When running "mvn package install pom.xml" I'm receiving the
>     following
>     >     error:
>     >
>     >
>     >     Tests in error:
>     >
>     >
>     testResponse(
org.jasig.cas.authentication.principal.GoogleAccountsServiceTests
>     >
>     >     )
>     >
>     >
>     testWithGoogleAccountsService(
org.jasig.cas.web.flow.DynamicRedirectViewSelect
>     >
>     >     orTests)
>     >
>     >
>     testNoService(
org.jasig.cas.web.support.GoogleAccountsArgumentExtractorTests
>
>     >     )
>     >
>     >
>     >     Tests run: 396, Failures: 0, Errors: 3, Skipped: 0
>     >
>     >
>     >     Any idea what's causing these problems?
>     >
>     >     Regards,
>     >
>     >     Philip
>     >
>     >     Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
>     >
>     >     _______________________________________________
>     >     Yale CAS mailing list
>     >     [email protected] <mailto:[email protected]>
>     <mailto:[email protected] <mailto:[email protected]>>
>     >     http://tp.its.yale.edu/mailman/listinfo/cas
>     <http://tp.its.yale.edu/mailman/listinfo/cas>
>     >
>     >
>     >
>     >
>     > --
>     > -Scott Battaglia
>     >
>     > LinkedIn: http://www.linkedin.com/in/scottbattaglia
>     > < http://www.linkedin.com/in/scottbattaglia>
>     >
>     >
>     >
>
------------------------------------------------------------------------
>     >
>     > _______________________________________________
>     > Yale CAS mailing list
>     > [email protected] <mailto:[email protected]>
>     > http://tp.its.yale.edu/mailman/listinfo/cas
>
>
>
>     Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
>
>     _______________________________________________
>     Yale CAS mailing list
>     [email protected] <mailto:[email protected]>
>     http://tp.its.yale.edu/mailman/listinfo/cas
>
>
>
>
> --
> -Scott Battaglia
>
> LinkedIn: http://www.linkedin.com/in/scottbattaglia
> <http://www.linkedin.com/in/scottbattaglia>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Yale CAS mailing list
> [email protected]
> http://tp.its.yale.edu/mailman/listinfo/cas


Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm

_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas




--
-Scott Battaglia

LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas

Reply via email to