[cas-user] Re: CAS Release/Security Announcements

2020-08-14 Thread Dustin J Luck
Looking at the blog, there is too much general info posted there to be useful for those of us looking solely for release and security announcements. On Friday, August 14, 2020 at 1:21:25 PM UTC-7 j-gar...@onu.edu wrote: > Dustin, > > I would check https://apereo.github.io/ > This is Apereo's bl

[cas-user] Re: CAS Release/Security Announcements

2020-08-14 Thread Dustin J Luck
Thanks for the info, Jeremiah. I was hoping not to have to set a reminder to myself to go and manually check something on a daily or weekly basis. When the mailing lists were being updated, it was great because it came to a place I'm already checking on a daily basis - my email inbox. On Frida

Re: [cas-user] Re: CAS Release/Security Announcements

2020-08-14 Thread Mike Osterman
I asked pretty much the same question as Dustin about a week ago: https://groups.google.com/a/apereo.org/g/cas-user/c/xTu0yzJQHBo I hope we don't have to use an RSS reader to get alerts about security vulnerabilities. To Dustin's (and my) point, the documented security announcement paths

[cas-user] Re: CAS Release/Security Announcements

2020-08-14 Thread Jeremiah Garmatter
Dustin, I would check https://apereo.github.io/ This is Apereo's blog, they last updated July 24th of this year discussing a vulnerability. On Friday, August 14, 2020 at 2:55:17 PM UTC-4 Dustin J Luck wrote: > Where is the proper place to get notifications for new CAS releases and > security

[cas-user] CAS Release/Security Announcements

2020-08-14 Thread Dustin J Luck
Where is the proper place to get notifications for new CAS releases and security announcements? I haven't seen anything from cas-announce since 10/28/19 or cas-appsec-public sinc

Re: [cas-user] Google SSO

2020-08-14 Thread Jeremiah Garmatter
Sweet, thanks for all this Richard, you've saved me a lot of headache. -Jeremiah Garmatter, Systems Administrator -Ohio Northern University, Class of 2020 -Work: 419-772-1074 Cell: 419-672-8685 -j-garmat...@onu.edu On Fri, Aug 14, 2020 at 12:06 PM Richard Frovarp wrote: > I think that's contro

Re: [cas-user] Google SSO

2020-08-14 Thread Richard Frovarp
I think that's controlled by the metadata, and my notes below say 1.1 unspecified. On Fri, 2020-08-14 at 12:03 -0400, Jeremiah Garmatter wrote: Ah, I see now. I should have mentioned that, in our case, the username is being sent to google as well, just through that attribute. When you set up goo

Re: [cas-user] Google SSO

2020-08-14 Thread Jeremiah Garmatter
Ah, I see now. I should have mentioned that, in our case, the username is being sent to google as well, just through that attribute. When you set up google's single sign on, did google's side inform you of the namespace they are expecting usernames to come in as? -Jeremiah Garmatter, Systems Admin

Re: [cas-user] Google SSO

2020-08-14 Thread Richard Frovarp
Yeah, you'll need to treat it like any other SAML2 service, including using the SamlRegisteredService configuration. Not entirely sure about attribute release. In our case, releasing the default username is all we need to make it work. But it should be like any other SAML2 service. The differen

Re: [cas-user] Google SSO

2020-08-14 Thread Jeremiah Garmatter
Richard, Thank you for the advice on this. We have started the creation process of our gsuitetest subdomain. While waiting for Google to verify ownership, I'd like to probe your brain some more. In the past (CAS 5.2), using that Googleapps SAML dependency allowed you to configure the Google se