Hi, Thanks for the feedback. Let me clarify though.
I did these two customisations for one of my customers and we talked with Misagh about the relevancy of integrating them in the Open Source project. So the question is: have you ever needed one of these two features? Thanks. Best regards, Jérôme Le sam. 27 mai 2023 à 00:50, Ray Bon <[email protected]> a écrit : > Feature 1: The second login should alert (or at least be configurable) the > user that the first login will be terminated and should trigger the SLO > process. The lost first TGT also happens with the DUO oauth2 process (not > with the iframe implementation), thus orphaning the ST records created > before DUO second factor and preventing those services from taking part in > SLO (we added some behaviour to the login flow to transfer the pre DUO > services to the post DUO TGT). > > Feature 2: The log in page could be displayed with a password field and an > uneditable username field filled with the current user's login id and a > link saying 'switch user' or 'if this is not you ...'. If the the user > wants to change the login id, then a warning is displayed saying that SLO > will be performed. > > Ray > > On Thu, 2023-05-25 at 11:08 +0200, Jérôme LELEU wrote: > > Notice: This message was sent from outside the University of Victoria > email system. Please be cautious with links and sensitive information. > > Hi, > > I'd like to make some kind of poll to know if some people might be > interested by the two following new features: > > Feature 1: I open the login page in two tabs of my browser and log in in > the first tab and then in the second tab: the second authentication > currently just erases the first one. Should we have better behavior? Like > displaying a warning to indicate that we keep the existing authentication > or replace it by a new one? > > Feature 2: I call the login page with the renew parameter. If the new > logged user is different from the old one, should I perform a SLO? > > Feedback will be welcome. > > Thanks. > Best regards, > Jérôme > > > -- > - 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/a/apereo.org/d/msgid/cas-user/3fdbc5e6f00342eb38f4a6f663f910c1988d4504.camel%40uvic.ca > <https://groups.google.com/a/apereo.org/d/msgid/cas-user/3fdbc5e6f00342eb38f4a6f663f910c1988d4504.camel%40uvic.ca?utm_medium=email&utm_source=footer> > . > -- - 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/CAP279LyWW7D6k1xJEUGv%2Bhd0w58fAQUK%2B66YStdcyGLnK2wrCQ%40mail.gmail.com.
