[cas-user] Re: CAS Initializr has v6.6.6 instead of v6.6.5
v6.6.6 is valid, it is a security release, https://apereo.github.io/2023/02/20/x509-vuln/ On Monday, March 6, 2023 at 11:13:04 PM UTC-6 jonan...@oru.edu wrote: > https://casinit.herokuapp.com/actuator/supportedVersions 6.6.6 > > https://github.com/apereo/cas/tags 6.6.5 > > Am I missing something? > > Thanks, > Jon > > > -- - 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 are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/f737d61b-fd4b-47c2-994c-5ea654aaff96n%40apereo.org.
Re: [cas-user] CAS 6.4 OIDC JWKS missing key fields?
I noticed my JWKS was missing a kid and causing weird results in one of the
OIDC libraries I use for testing.
I just added the kid to my key in the "keystore.jwks" manually. I just
generated a uuid4, but you can use any ID unique to your keystore from what
I understand.
The kid then appears on the endpoint.
Thanks,
Carl Waldbieser
ITS
Lafayette College
On Tue, Mar 7, 2023 at 12:13 AM Yan Zhou wrote:
> Hi,,
>
> CAS 6.4 OIDC JWKS endpoint looks like this. Our vendor has problem with
> its missing fields such as alg, kid, and use.
>
> Anyone knows how to show these fields in JWKS? They showed us what Okta
> and Google OIDC provider presents, yes, they do have these fields.
>
> This probably affects OIDC JWT access token header attributes as well.
>
> Thanks,
> Yan
>
> {
>
> "keys":
>
> [
>
> {
>
> "kty":"RSA",
>
> "n":"pwNNGZn0..RW18eq6Asiw",
>
> "e":"AQAB"
>
> }
>
> ]
>
> }
>
> --
> - 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 are subscribed to the Google Groups
> "CAS Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to cas-user+unsubscr...@apereo.org.
> To view this discussion on the web visit
> https://groups.google.com/a/apereo.org/d/msgid/cas-user/a816b9c5-662f-4a75-b87e-414f350df5d3n%40apereo.org
>
> .
>
--
- 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 are subscribed to the Google Groups "CAS
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit
https://groups.google.com/a/apereo.org/d/msgid/cas-user/CALt4NbNZ%2B6%3DNbtqSVAbge%2Bm%3DUbhSNrkGCEP4qYSXNpmaRDWHKw%40mail.gmail.com.
[cas-user] Re: CAS 6.4 OIDC JWKS missing key fields?
Hi,
we had a similar issue a few weeks ago with
https://github.com/bigbluebutton/greenlight.
We generated a new JWKS file using the generate-oidc-jwks command available
in
https://apereo.github.io/cas/6.6.x/installation/Configuring-Commandline-Shell.html
Guillaume
Le mardi 7 mars 2023 à 06:13:03 UTC+1, Yan Zhou a écrit :
> Hi,,
>
> CAS 6.4 OIDC JWKS endpoint looks like this. Our vendor has problem with
> its missing fields such as alg, kid, and use.
>
> Anyone knows how to show these fields in JWKS? They showed us what Okta
> and Google OIDC provider presents, yes, they do have these fields.
>
> This probably affects OIDC JWT access token header attributes as well.
>
> Thanks,
> Yan
>
> {
>
> "keys":
>
> [
>
> {
>
> "kty":"RSA",
>
> "n":"pwNNGZn0..RW18eq6Asiw",
>
> "e":"AQAB"
>
> }
>
> ]
>
> }
>
--
- 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 are subscribed to the Google Groups "CAS
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit
https://groups.google.com/a/apereo.org/d/msgid/cas-user/699bd63e-b4c4-4df6-8d93-5b6c0127c7e7n%40apereo.org.
