Forget this for now .. I had checked the documentation to see if it were an
Abstract class and then promptly overlooked my results.
I am trying some things now.
Linda Toth
University of Alaska - Office of Information Technology (OIT) - Identity
and Access Management
910 Yukon Drive, Suite 103
Fai
RE:
Distinct Principal Resolvers We began this process with CAS 3.4.2.1. We
have not upgraded simply because we are still at the soft roll out stage
and don't want to make any adjustments that may occur based on later
versions.
So, I think I actually don't need two different principal resolvers,
Marvin
This does help - thanks
Linda Toth
University of Alaska - Office of Information Technology (OIT) - Identity
and Access Management
910 Yukon Drive, Suite 103
Fairbanks, Alaska 99775
Tel: 907-450-8320
Fax: 907-450-8381
linda.t...@alaska.edu | www.alaska.edu/oit/
On Sat, Mar 8, 2014 at 3:3
> I think the CredentialsToLDAPAttributePrincipalResolver is the one that must
> be different for multiple LDAPs.
That's correct. The inner
UsernamePasswordCrednetialsToPrincipalResolver is used to seed the
LDAP query with the user name used in the LDAP search filter, but
CredentialsToLDAPAttribut
Marvin, et al
Sorry, I picked the wrong Principal Resolver bean to ask about.
The configuration Ellucian uses is
PrincipalBearningCredentialsToPrincipalResolver
CredentialsToLDAPAttributePrincipalResolver, and then within that
UsernamePasswordCrednetialsToPrincipalResolver.
I think the Credenti
Thank you ..
This confirms what I was arriving at.
Our use case is that we have an AD LDAP which expires accounts based on
individual campus policy. But the application we are configuring CAS for
provides information concerning W2 forms, transcripts, class history, etc.
They do not want to bump
> I am not sure why Ellucian did not make use of a key-ref, but there it is.
> I think an explanation of why attribute filters are defined in both places
> would be of great help to me .. this has always been murky in my
> understanding.
I've read your original post a couple times and I'm not enti
Folks,
I have been thinking this over and it seems to me the substitution will do
the same thing as what Ellucian repeats in the Authentication Manager.
Please correct me if I am wrong.
I am not sure why Ellucian did not make use of a key-ref, but there it is.
I think an explanation of why attri
Folks,
I am sorry to post so much detail, but I am not entirely sure why I have
the repetitive elements in the prescribed changes to
deployerConfigContext.xml by Banner, which in turn are causing me to feel
uncertain of where to place statements.
Ellucian repeats the filters for a principal iden
