<admit> So I found out that I was my shell script wasn't running the mvn
clean package like I had thought so when I was "deploying" the edits, my
changes were not really being deployed. I undid all the new edits (putting a
slash before the classpath) and it seems to work just fine. I am unsure what
initially caused the issue, but it seems to be fine now.

TLDR - my deploy.sh wasn't rerunning mvn package and therefore the changes
were not really being applied. Thanks for helping me out, sorry it wasn't an
actual problem.


Regards,
Patrick

-----Original Message-----
From: Marvin S. Addison [mailto:[email protected]] 
Sent: Monday, February 27, 2012 12:33 PM
To: [email protected]
Subject: Re: [cas-user] No bean named 'privateKeyFactoryBean' is defined

> Thank you for the response. I changed the p:location to be
> classpath:/private.p8. I don't see it mentioned in the stack trace either.

This is really odd.  I've carefully reviewed your config and don't see 
anything wrong in the Spring wiring.  Can you verify that the private.p8 
file is written to the filesystem where you'd expect for a WAR deployed 
to your Tomcat container?  Are the file permissions such that the Tomcat 
process can read it?  I'm still thinking this is a factory bean creation 
issue since there's nothing patently wrong with your config.

Maybe you can try the following to see if there's a different error message:

<bean name="googleAccountsArgumentExtractor"
       class="org.jasig.cas.web.support.GoogleAccountsArgumentExtractor"
       p:httpClient-ref="httpClient"
       p:alternateUsername="EmailAddress">
   <property name="privateKey">
     <bean
       class="org.jasig.cas.util.PrivateKeyFactoryBean"
       p:location="classpath:private.p8"
       p:algorithm="RSA" />
   </property>
   <property name="publicKey">
     <bean
       class="org.jasig.cas.util.PublicKeyFactoryBean"
       p:location="classpath:public.key"
       p:algorithm="RSA" />
   </property>
</bean>

M

-- 
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to