I'm trying to use the new multiple-SAML client capability in 5.1, and it looks like all of the clients will show up as "SAML" on the login page (and "SAMLClient*x*" internally). It would be helpful to have the client name be a deployer-settable (optional) property, something like:
cas.authn.pac4j.saml[0].clientName = This Org cas.authn.pac4j.saml[1].clientName = That Org ... and if the property is not set, we'd default to the usual SAMLClient*x* nomenclature. Looking at the code, it looks like most of the effort will be in setting up the configuration model and a line or two in Pac4jAuthenticationEventExecutionPlanConfiguration. Should I enter an issue for this on github? Thanks, Rich -- - 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/CAMYXOV95%2Bi%2BB6kONxUu7TxtSDmDnnR3yiy7ktVw2Eou6-sg5pQ%40mail.gmail.com.
