It looks like an issue from tasks.gradle and the path separators:
projects\cas-overlay-template\build/cas-resources
which causes string mismatch with
def toResourceFile = resourceFile.replace(fromFile, resourcesDir)
I added/modified to the task.gradle file getResource function:
def resourcesDir
Hi Nikolas,
Si after looking tour configuration, nom it's not "normal". Claims should
ne appear on thé top level ans not un an attributs claims.
First, try to remove your attributeReleasePolicy un you service.json.
Also I haven't test 6.2, I'm still In 6.1. So maybe it's an improvement,
but "
Ray,
I'll try it but the public key for it already is as it's the same cert.
I was using for the /cas deployment itself in an external tomcat
deployment. It was complaining about un-trusted certs until I did that.
Coln
On 8/24/20 3:47 PM, Ray Bon wrote:
Colin,
Maybe add your certificate
Colin,
Maybe add your certificate to the java ketstore.
https://docs.oracle.com/cd/E54932_01/doc.705/e54936/cssg_create_ssl_cert.htm#CSVSG180
Ray
On Mon, 2020-08-24 at 15:25 -0400, Colin Ryan wrote:
Notice: This message was sent from outside the University of Victoria email
system. Please be
Folks,
So I've still not managed to move past this. Even even started from scratch.
git clone https://github.com/apereo/cas-management-overlay.git
git checkout 6.0.x
./build.sh clean
./build.sh run - breaks because it can't seem to find some of the
required components for the 6.0.x
Thanks, Ray! I appreciate the pointer. It's nice to have another lead to
chase down.
On Mon, Aug 24, 2020 at 9:41 AM Ray Bon wrote:
> Mike,
>
> This sounds like a proxy failure. The user successfully logs in, but when
> a proxy ticket is required, there is a failure and the user is returned to
In our CAS environment, some services need to authenticate users using LDAP
(Active Directory) and others need to authenticate through delegation with
Azure.
Ideally, the we'd like to have the user be presented with only a single
login form on the CAS login page. With the delegated
In our CAS environment, some services need to authenticate users using LDAP
(Active Directory) and others need to authenticate through delegation with
Azure.
Ideally, the we'd like to have the user be presented with only a single
login form on the CAS login page. With the delegated
Hello,
I am using cas overlay template and i have configured cas as oauth2 server.
it works perfectly. but, when i change the jwt sign key size (default 512
https://github.com/apereo/cas/blob/master/api/cas-server-core-api-util/src/main/java/org/apereo/cas/util/crypto/CipherExecutor.java)
to
Mike,
This sounds like a proxy failure. The user successfully logs in, but when a
proxy ticket is required, there is a failure and the user is returned to the
log in page (am I understanding correctly?).
Check your access logs for Canvas and cas to see if communication is successful
when a PT
Hey denizg,
first thanks for you suggestion. But I actually want SLO. I want to destroy
the SSO session and not only the application session. I also configured
front channel to make it work.
No, the problem is something different: If I use delegated SSO provider
like Google or GitHub to
I realized that It were because of different algorithm types. spring
resource server uses hmacsha256 default when using symmetric key, but cas
sends hmacsha512. so i updated accessTokenConverter() method like below;
@Bean
public JwtAccessTokenConverter accessTokenConverter() {
Jeremiah,
Sorry for long time of response.
For exemple, if you want to integrate dependency from CAS to connect to a
database, you should use the same version of spring otherwize you got an
error.
For CAS 6.1.x :
https://github.com/apereo/cas/blob/6.1.x/gradle.properties#L94 with
CAS-Manager
edit: single sign on out
dyte gyte , 24 Ağu 2020 Pzt, 11:46 tarihinde şunu
yazdı:
> Hello,
>
> afaik, there are 2 logout type: single logout and single sign-on. the
> default behavior is single logout which means that if you logout current
> app, you also logout all applications that cas is
Hello,
afaik, there are 2 logout type: single logout and single sign-on. the
default behavior is single logout which means that if you logout current
app, you also logout all applications that cas is connected. this is the
situation you are facing. but you need single sign on as i understand.
Hey guys,
we noticed some new behavior with delegated SSO authentication. When I
login with my Google SSO account at our CAS and logout again, I am not only
logged out from CAS but also from my Google account. This also happens with
delegated GitHub SSO.
We are using CAS 6.2.1 but I am unsure
16 matches
Mail list logo
