Hi all,
I'm trying to develop a new module authentication for CAS 5.3.x. This new
module supports to authenticate by Face Recoginition which is existing
services.
I'm developing this module "cas-server-support-face" by copy source code
"cas\cas-server-support-ldap" and modify it.
I don't
Everyone let me ask.
How to add a new module to authenticate to cas server 5.3?
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you
Question on AD memberOf CAS multiple attributes:
We are configuring CAS 5.3. In a service registry .json file, within the
"ReturnMappedAttributeReleasePolicy" allowed attributes, the memberOf array
comes across from AD where each of the multiple attributes are enclosed in
separated tags:
Hi,
I'm not sure it helps in your case, but we had a similar issue with
some applications:
- the application creates a session and store information before going to CAS
- the application redirects to CAS which asks password
- CAS redirects to the application
- the user clicks on "back" button
Julien,
Check this setting:
cas.view.defaultRedirectUrl=https://${cas.server.name}/mypage
If user goes to CAS first (without a service), they get redirected to
defaultRedirectUrl.
Ray
On Wed, 2019-04-17 at 16:56 +0200, Julien Gribonvald wrote:
Hi,
Is there a simple way to force user to
Hi,
Is there a simple way to force user to come from a service before to
authenticate ?
I mean before accessing to some services (not all) a user should come
from an entry point (a service on which he will be authenticated after,
like a portal), if not he should be redirected to this entry
Hi,
After investigations, it seems that it's an issue on the CAS Client side
(owncloud CAS client)
CAS Client response to the SLO BACK_CHANNEL resquest is 405 Method not
allowed
[09/Apr/2019:00:05:57 +0200] "POST /cloud/index.php/apps/user_cas/login
> HTTP/1.1" 405 - "-"
At least on CAS 5.2.x with a Mongo DB service registry, the way you did it
was:
1. Edit the dependencies in pom.xml and:
1. REMOVE the cas-server-support-json-service-registry dependency
2. ADD the cas-server-support-mongo-service-registry dependency
2. Rebuild the server.
3.
I've got a demo cas instance which worked well using JSON service
registries, but I want to migrate the registry to DynamoDB (among other
things to deliver a HA solution.)
What's not entirely clear is how I convert the JSON files into objects that
can be put into the database.
I see there is
