sorry for my skim read :)
Le jeu. 27 févr. 2020 à 09:23, Napoleon Ponaparte
a écrit :
> No Mr Jérôme Steve,
> I deployed CAS behind HA Proxy. It's done.
> Now I want to register service CAS Managment Web App with proxy.
> On Thursday, February 27, 2020 at 3:15:5
> You will want to turn logging up (debug or trace) for CAS, and memcached.
> Also check access logs.
> On Wed, 2020-
With thymeleaf template you can get directly env var by using this :
Le ven. 7 févr. 2020 à 16:04, Nathan Lewan a écrit :
> i've been trying to get environment variables to resolved when added to my
ou find out what specifically CAS is storing in the http
>> session for OIDC that needs to be replicated? I think I have seen the same
>> issue in my deployment where OIDC wasn't working in an active/active CAS
>> cluster but I haven't had a chance to track down the cause.
This is a spring framework warning :
If you are using overlay add this dependency in your build.gradle file :
> Is that the case? Or did you set up multiple nodes between the logs from
> node 1 and node 2?
> On Tue, 2020-01-07 at 08:02 -0800, Jérôme Steve wrote:
> Hi ray,
> Thanks for your reply. so you think the problem come from my OIDC client
> app ? o
1. In my opinion don't use gradle run in production but launch your war
with java directly (Like in the dockerfile cas overlay).
2. response in 1. maybe solve this porblem ?
Le jeudi 9 janvier 2020 16:12:21 UTC+1, crdaudt a écrit :
> I will restate my questions:
>1. What is
Look at this :
Le mar. 21 janv. 2020 à 18:05, mohamed gamal a
> Hello everyone,
> I know this is a weird situation. But we have faced
I think you have to used the same ticket registry for the two organisation.
You have lot of kind of ticket registry (
Of course the users need to have the same login in the two
s nodes/network so how the
> token created by on of theme will be see by the other with the same tiket
> registery ? Do you have a POC I can turn and deploy to thow tomcats
> Le mardi 14 janvier 2020 12:08:53 UTC+1, Jérôme Steve a écrit :
Before all thanks for your works.
We are using CAS overlay in Multi node architecture (Docker container) behind a
load balancer and a proxy with a memcahced service registery.
All work fine but when we used it like an OIDC provider, i'm getting a
Validation Ticket Failed after called
> On Fri, 2020-01-03 at 02:37 -0800, Jérôme Steve wrote:
> Before all thanks for your works.
> We are using CAS overlay in Multi node architecture (Docker container) behind
> a load balancer and a pr
I think what you use, is not what you discribe.
Enter code here...
This is for define a static attribute "udcid" with value "UDC_IDENTIFIER".
You try to add the scopes in your service configuration ? like this :
"scopes" : [ "java.util.HashSet", [ "openid"] ]
Le mer. 20 mai 2020 à 12:35, Charl Thiem a écrit :
> Hi there
> I tried that too with no luck. I think there is a bug in spring's pac4j or
> pac4j itself. I had
Your OIDC configuration look good.
You map your claims like this :
Maibe you don't have sn and email in your attribute repository ?
Le lun. 8 juin 2020 à 16:37, qla3fa a écrit :
> I try to configure OIDC with
You have to pût it un the attributsrRepository from jour db or ldap. After
you can get it, in ths jwt token.
Something l'île this :
Le jeu. 4 juin 2020 à 16:25, dg a écrit :
> hello, i am really stuck with
Sorry in english,
You have to put it in the attributes repository from our db or your ldap
(or something else). After that you can get it in the jwt token.
Something like this :
Le jeu. 4 juin 2020 à 16:25, dg a écrit
0 module too and I use and map
> these attributes with success... So I think it's ok with these attributes.
> It's only with OIDC services it doesn't work...
> Best regards.
> Le 08/06/2020 à 18:01, Jérôme Steve a écrit :
> Your OIDC configur
I had the same probleme. What I notice :
If you coment or you remove property in app.properties, the corresponding
env var is used.
But if you have it in the app.properties, property will not be erasse by
But for me is same as other spring-boot app. Maybe what you are
Ok all look good.
So what is that :
you don't need it in /cas/oidc/authorize
And when you talk about "In *userinfo* endpoint I getting now" what is your
Hi, You see it here : /cas/oidc/.well-known ?
Le ven. 26 juin 2020 à 09:07, Jakub Fridrich <
jakub.fridr...@klikpojisteni.cz> a écrit :
> Thanks, but attributes not showing still..
> My service now looks like:
> "@class" : "org.apereo.cas.services.OidcRegisteredService",
Ok maybe you need it in response, but not when you request Authorization.
Le ven. 26 juin 2020 à 15:20, Jakub Fridrich <
jakub.fridr...@klikpojisteni.cz> a écrit :
> Yes, for userinfo endpoint I think */cas/oidc/profile*.
> For claims, I need this params, generated with XWiki. The above claim
I think your need to add "logoutUrl" : "yyy" property in the
Le mar. 28 juil. 2020 à 21:34, Yan Zhou a écrit :
> cas/logout does work, but it does not redirect back to the app URL, the
> OIDC standard uses this:
I think you have to map your custom user attributes from attribute
repository, to your claims/scope oidc :
Le lun. 20 juil. 2020 à 20:55, Yan Zhou a écrit :
> I have CAS5.3.x,
Mail list logo