Jeremiah, I get regular requests from vendors wanting test users. We have a separate ou for our test users. You can add additional cas.authn.ldap sections (and attribute lookup, if necessary). They are searched in order, so it should not impact your regular lookups.
Ray On Wed, 2020-12-16 at 05:40 -0800, Jeremiah Garmatter wrote: Notice: This message was sent from outside the University of Victoria email system. Please be cautious with links and sensitive information. Hello, I am running CAS 6.2.1 with attributes fed from an LDAP directory. A vendor has requested a temporary account to test with while they set up a new service. I was wondering if there was a way to make a temporary account within CAS instead of creating one in LDAP? My LDAP servers feed into several other systems on campus and I'd rather not propagate this temporary account all over. I remember having to disable the default CAS user, is this just a matter of re-instating that account or could that mess with my LDAP authentication? -- Ray Bon Programmer Analyst Development Services, University Systems 2507218831 | CLE 019 | [email protected]<mailto:[email protected]> I respectfully acknowledge that my place of work is located within the ancestral, traditional and unceded territory of the Songhees, Esquimalt and WSÁNEĆ Nations. -- - 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/8031d5ca605aac6d5d95f55cf833421f46c39dcb.camel%40uvic.ca.
