Marvin,
Thank for the response. The configuration is actually correct. In my
example I am using /login as my context root. After some more
investigation I actually narrowed the problem down to the ticket registry.
What I noticed was that the ticket was being deleted right after it was
being created. When I use the below configuration it does not work:
<bean id="ticketRegistry"
class="org.jasig.cas.ticket.registry.JpaTicketRegistry">
<constructor-arg index="0" ref="entityManagerFactory" />
</bean>
<bean id="ticketRegistryCleaner"
class="org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner"
p:ticketRegistry-ref="ticketRegistry"
p:lock-ref="cleanerLock"
/>
<bean id="cleanerLock"
class="org.jasig.cas.ticket.registry.support.JdbcLockingStrategy"
p:uniqueId="${host.name}"
p:platform="${ticket.cleaner.database.platform}"
p:applicationId="cas-ticket-registry-cleaner"
p:dataSource-ref="dataSource"
/>
<bean id="ticketRegistryCleanerJobDetail"
class="org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean"
p:targetObject-ref="ticketRegistryCleaner"
p:targetMethod="clean"
/>
<bean id="periodicTicketRegistryCleanerTrigger"
class="org.springframework.scheduling.quartz.SimpleTriggerBean"
p:jobDetail-ref="ticketRegistryCleanerJobDetail"
p:startDelay="20000"
p:repeatInterval="1800000"
/>
If however I switch to back to the default below config it works fine:
<bean id="ticketRegistry"
class="org.jasig.cas.ticket.registry.DefaultTicketRegistry" />
<bean id="ticketRegistryCleaner"
class="org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner"
p:ticketRegistry-ref="ticketRegistry" />
<bean id="jobDetailTicketRegistryCleaner"
class="org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean"
p:targetObject-ref="ticketRegistryCleaner"
p:targetMethod="clean" />
<bean id="triggerJobDetailTicketRegistryCleaner"
class="org.springframework.scheduling.quartz.SimpleTriggerBean"
p:jobDetail-ref="jobDetailTicketRegistryCleaner"
p:startDelay="20000"
p:repeatInterval="5000000" />
At this time we are only using one CAS server. I can see this becoming an
issue in the future, but for now I am just using the in-memory version.
On Fri, Jan 13, 2012 at 9:15 AM, Marvin Addison <[email protected]>wrote:
> > to the CAS via the url https://localhost/login/login
>
> That URL looks incorrect. It's either a typo or perhaps indicative of
> configuration problems.
>
> > using an account with ROLE_ADMIN privileges. If I then go to
> > https://localhost/login/services/manage.html, it redirects me to a login
> > page.
>
> Turn up the org.jasig.cas category to DEBUG and post the relevant
> logs. See https://wiki.jasig.org/display/CASUM/Logging for help with
> logging configuration.
>
> 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
>
>
--
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
