Hi,
I'm new on this mailing-list. I've install cas on one server and i plug on
different web application.
I configure cas with Ldap and we have declare 2 ldap server.
One search on mail=%u (users can logon with her mail address)
One search on employeeID=%u (users can logon with her id)
The
ticket 'ST-6-WfLwVOA4EJRi7Qnb0m7H-cas' not recognized
the CAS logs show that the ticket was not found in the ticket registry and
therefore the ticket passed in wasn't valid.
Is there a corresponding log entry that indicates the ticket was
issued to the service for which you're trying to
Best I can do is cite our overlay where we have CAS 3.4.11 integrated with BEIS:
https://svn.middleware.vt.edu/svn/middleware/cas/cas-server/trunk/
M
--
You are currently subscribed to cas-user@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives,
You replaced the existing bean that stores usernames. That's wrong.
I highlighted the ONE line that needed to be changed.
Cheers,
Soctt
On Mon, Nov 14, 2011 at 12:57 PM, Scott Battaglia scott.battag...@gmail.com
wrote:
Sorry, we've apparently got out of date config.
You should replace just
Scott,
To be sure I'm clear on what you are referring too.
You're saying that the current config that I have (below) is incorrect?:
bean id =userDetailsService
class=org.acegisecurity.userdetails.memory.InMemoryDaoImpl
property name=userMap
value
Yes, only the username changed. You're using CAS to control access to the
Services Management Tool, so nothing sees your password OTHER than CAS.
Therefore, the value in the Spring Security configured item is not used.
This would be the same as if you used Spring Security in any of your
Scott,
I have reverted my configuration back to the way you have specified:
sec:user-service id=userDetailsService
sec:user name=admin password=test authorities=ROLE_ADMIN /
/sec:user-service
When I use this, I get an error message on the services page that says:
The credentials you
That is CAS telling you that the whatever you entered for the username and
password was wrong.
In case there is any confusion, what you just updated in no way affects CAS
log in. It just affects access to the Services Management Tool.
On Tue, Nov 15, 2011 at 11:31 AM, Ben Branch
You should login to CAS with the username admin and whatever your
password is for admin in your authentication backend, NOT the password
test. The password provided in:
sec:user name=admin password=test authorities=ROLE_ADMIN /
is not used by CAS - it always uses your authentication backend.
I am seeing this error when I try to login to uPortal with CAS:
http://pastebin.com/tnpn6Aui
I'm using my custom overlay with CAS 3.4.2.1
Is it a dependency issue? Here is my dependency tree:
http://pastebin.com/SVBYFrRZ
How would I fix this?
--
You are currently subscribed to
Hello Everyone,
We are in process of implementing CAS server at our school. We currently
use third party .net portal that resides on top of our SIS. We were able to
casify the web.config but now the issue is that we cant authenticate users
because passwords are encrypted in the portal database.
I don't see much explanation in the logs that would explain why the
service ticket isn't found in the registry at validation time -- it's
clearly created beforehand:
2011-11-14 09:23:24,699 DEBUG
[org.jasig.cas.ticket.registry.DefaultTicketRegistry] - Added ticket
[ST-2-ylhhsn0wTAgC3gdE6j2y-cas]
The vendor has provided us with an Authentication API.
Red flag. The vendor ought to document the encryption system used to
secure credentials. Anything based on a standard ought not need a
proprietary third party API. You should press your vendor a bit for
more information.
Has anyone ever
Hi Faisal,
Have you reviewed the QueryDatabaseAuthenticationHandler class? With that,
you should be able to provide your own password encoder by extending the
DefaultPasswordEncoder using the authentication API to possible encrypt the
password before the query is executed.
Please see this
Andrew/Scott,
Okay, I have my Service Manager up and running. I can also log into it and
add/delete services. I can't thank everyone enough for the help I've received
on this list. So to be clear on the user-sec usage (within an Active
Directory configuration of CAS 3.4.10):
sec:user
Everyone,
I'm reading over some of the HA documentation and the majority of seems geared
towards 3.0.6, 3.1.0, and 3.2.0. While all say it is supported on the greater
versions, I've seen the documentation vary across different releases. Has
anyone used the current guide on 3.4.10? Were
Hi Ben,
We followed the guide and implemented an High Availability CAS server
using JPA-based Ticket Registry for version 3.4.10.
It was pretty straight forward as far as I recall.
Mahmudul Hasan,
System Support Specialist,
University of Lethbridge,
Alberta, Canada
On Tue, Nov 15, 2011 at
17 matches
Mail list logo
