Well, my project allows me to use RC version, so I know that 5.2.0-RCx have a lot of improvement, and one of them is allow customization of naming in a lot of places (like pac4j items, different authentication handler, and more), so I can't think of a good solution to implement those changes into 5.1.x.
Maybe you might tries copy the part of 5.2.0-RC and overlay them in the project? -Andy On Tuesday, 10 October 2017 15:50:39 UTC+8, Filip Majernik wrote: > > This is exactly what I would need (assuming that the clientName parameter > is then used for the typedId). However, I probably cannot use the RC > version (policy reasons). Is there any workaround around this? > > On Tuesday, October 10, 2017 at 3:40:05 AM UTC+2, Andy Ng wrote: >> >> For orgin, if you don't mind to use 5.2.0-RCx: >> *Pac4j:* >> you can see this ( >> https://apereo.github.io/cas/development/installation/Configuration-Properties.html#facebook >> ) >> You can see that there is a field called [clientName], which actually >> will let you define the name of your pac4j providers. >> But even if you don't specified the clientName, the name of the pac4j >> provider is also given by default. Like "FacebookProfile" as you cited >> above. >> >> *SAML for Google or for other things:* >> You can see that ( >> https://apereo.github.io/cas/development/installation/Configuration-Properties.html#saml-sps >> ) >> The name will be the origin of the samle >> >> *LDAP:* >> This :( >> https://apereo.github.io/cas/development/installation/Configuration-Properties.html#why-passivators >> ) >> #This should be what you need >> # cas.authn.ldap[0].name= >> >> >> About the ID and your other question, idk how to do it using traditional >> configuration. You can also opt for custom authentication handler like you >> said about, here some reading that might be useful ( >> https://apereo.github.io/2017/02/02/cas51-authn-handlers/) >> >> Hope this helps you, >> - Andy >> >> On Monday, 9 October 2017 18:47:16 UTC+8, Filip Majernik wrote: >>> >>> I am using CAS to authenticate users for a service, which contains user >>> profiles. I need to map this user profiles to the users, i.e. I need a >>> unique user identifier, which I get from the authentication. This is more >>> or less provided by the CAS, however I also need to store the information >>> where the user comes from (or which authentication provider did he use - >>> internal one, external SAML, oAUTH, LDAP, etc...). Is there any >>> configurable way how to do this? I think I could override >>> the AbstractPreAndPostProcessingAuthenticationHandler.postAuthenticate() >>> method and try to retrieve some information from the credentials. >>> >>> Another problem which I face in this context is, that prior to the >>> authentication I need a mapping of the user profiles to the users. This >>> needs to be imported by the system administrator, however he needs to know >>> the unique IDs which CAS will be returning for the users. From the >>> documentation for the delegated authentication: >>> >>> - An identifier which is the profile type + # + the identifier of >>> the user for this provider (i.e FacebookProfile#0000000001) >>> >>> Is there any ENUM or anything which identifies the providers inside the >>> CAS? I need to have a list of profiles with at least these attributes: >>> >>> - ID of the user (must be unique throughout the CAS) >>> - origin - unique identifier of the system or authentication >>> handler, i.e. LDAP, SAML 2.0 for Google, SAML 2.0 for Facebook, etc.... >>> >>> >>> -- - 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/df9efd28-1c2f-4672-b956-16f5e2bb1ec9%40apereo.org.
