On 07/18/2017 03:56 PM, Richard Frovarp wrote:
We are going to try to switch Google authentication over to CAS
Thursday morning. I've done the configuration in CAS and have read the
documentation. Anything I need to watch out for? Anything I should be
specifically testing when I do this? It looks dead simple, just want
to make sure I'm not missing anything.
Thanks.
Richard
Follow up to my own message, yes it is that simple. In my testing I did
discover a couple of items:
- Global admins don't appear to follow the workflow
- Google MFA does not trigger after login. Slight issue as we are only
licensed for employees via Duo, which we have working in CAS.
- Transition to SSO did not interfere with existing devices / apps
already logged in, at least not for our short testing window.
- iOS keyboard on iPhone doesn't show a period for a CAS login. All of
our ids have periods in them.
- iOS keyboard triggers the caps lock warning after the upper case
character is entered, at which point the keyboard is back in lowercase
mode despite the caps lock warning.
- iOS doesn't wrap the login button with any sort of button visual
indicator.
Those last three are due to the fact I don't use iOS, but did so this
morning for testing. Last one might be on us as we have customized the
login page.
Overall quite happy with how easy that integration makes it and how well
it works.
--
- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation website: https://apereo.github.io/cas
- CAS project website: https://github.com/apereo/cas
---
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 on the web visit
https://groups.google.com/a/apereo.org/d/msgid/cas-user/3cd09b1c-865f-0ccf-2e97-54fb931267c7%40ndsu.edu.
