Removing the cas.ticket.registry.jpa.crypto.* properties has resolved my 
OIDC logic issue also. Thank you for the help.

On Monday, 5 May 2025 at 15:07:26 UTC+5:30 Ruggiero Dibenedetto wrote:

>
> Hi don't know if it works for you. But my problem is fixed deleting the 
> following properties from cas.properties:
> cas.ticket.registry.jpa.crypto.signing-enabled
> cas.ticket.registry.jpa.crypto.signing.key
> cas.ticket.registry.jpa.crypto.signing.key-size
> Il giorno domenica 4 maggio 2025 alle 18:43:40 UTC+2 Aniket Gangadharan ha 
> scritto:
>
> Hi,
> Did anyone find a solution to this? I am also facing the same issue.
> The internal redirection on cas with the login takes place and then when 
> redirecting back to the client the parameters for code and state is not 
> redirect in the HTTP 302.
> Tested with CAS 7.2.1 version
>
> Thanks,
> Aniket
>
> On Tuesday, 15 April 2025 at 06:13:58 UTC+5:30 Ruggiero Dibenedetto wrote:
>
> Hi all,
> I'm having some problem with the configuration of OIDC with cas 7.1.3. 
> The old version I have, 5.3.16 works fine.
>  
> With the new version instead, I start from the similar request, but at the 
> end I don't have the same redirect, and I lost al the parameters in the 
> link that I use on my java application.
> I have this workflow: 
>
>    - 
>    
> ..../oidc/oidcAuthorize?scope=scopevalue&response_type=code&redirectUri=redirectUri&state=stateValue&nonce=noncevalue&clientid=clientValue
>    - Then seems work fine with the login, mfa etc.
>    - 
>    
> /oauth2.0/callbackAuthorize?clientId....scope....redirecturi....responseType....state....nonce...clientname...ticket
>    - And the location of this last link, is just the redirect uri. 
>
> Instead in the version 5.1.16 the last redirect workflow is:
>
>    - oidc/authorize
>    - all the stuff for the login
>    - oauth2.0/callbackAuthorize with all the parameters
>    - /oidc/authorize with a location that contains the parameters state 
>    nonce code
>
> And after the redirect of the authorize I can read also the authorization 
> code and so validate the session.
>
> But with the new version this last step is not present. 
>
> Do you have any suggestion or example on how it should work?
>
> Thank you
>
>
>

-- 
- Website: https://apereo.github.io/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/86ea3d4e-e123-4c3e-b542-93b2382a234fn%40apereo.org.

Reply via email to