I'm not sure if this would be less secure than any other service at least from a brute force perspective. The user still has to log in to your CAS instance. If you want to prevent brute forcing, you should employ some sort of account lockout after so many failed attempts or the CAS authentication throttling module (https://apereo.github.io/cas/7.0.x/authentication/Configuring-Authentication-Throttling.html). It could be problematic if you release several user attributes to the localhost serviceID though. Then anyone could receive the user info to their local service after a successful authentication.
I am a little confused how this would work from a technical standpoint. I don't know the CAS protocol that well, but if the CAS server has to communicate with the localhost service could there be a chance that communication breaks down as CAS tries to communicate with it's own localhost? On Friday, July 12, 2024 at 4:53:04 AM UTC-4 jehan procaccia wrote: > Hello > > developers ask us to allow serviceID of type https://localhost/* or > https://127.0.0.1/* in order to allow them to develop on their local > machine ans test locally . > As system and network administrators we are afraid that this opening of > localhost serviceID might allow the entire world ( all Internet connected > device and hence hackers !) to access our CAS server, allowing them for > example to brute force the web login interface or whatever other mischief > possible . > Is this a real security breach to allow serviceID like https://localhost/* > , or we are anyway already exposed by our production services which allows > https://*.our-domain.fr/* serviceID which could be also used by hackers > if the spoof our urls ? > > thanks for your security advice regarding this question . > > -- - 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/7796936a-084c-4ef2-9ab0-ca2a25d2feefn%40apereo.org.
