The root of the problem is that the authentication request doesn't
contain the principalIdAttribute, which you've defined as 'uid':
> request=[org.ldaptive.auth.AuthenticationRequest@1438545291::user=myuser,
> retAttrs=[]]
So the authenticated entry doesn't contain that attribute either:
> [org.ld
Hi Dmitriy,
Thanks again for the help.
Below is the relevant config from deployerConfigContext.xml, with a few of the
surrounding lines for context. Although "passwordhash" appears in the sql
statement, this is a plain text field in the db at the moment.
In testing 4.x I’m trying to understand the LdapAuthenticationHandler’s use of
the principalIdAttribute and why I’m not getting expected results.
Using the documentation for LDAP setup, I have the following:
With this, the principalID is not being set
Thanks,
I've temporarily been diverted from working on this issue, but will try this
fix when I put back on it.
Patrick
-Original Message-
From: Stefan Paetow [mailto:stefan.pae...@ja.net]
Sent: Thursday, July 17, 2014 6:08 AM
To: cas-user@lists.jasig.org
Subject: RE: [cas-user] Redire
Hello,
I'm trying to upgrade from 3.4.10 to 3.5.1 and move to the war overlay method
at the same time. I've got it most of the way set up, but when I try add ldap
authentication I run into trouble. I've included errors and config information
below. Any help would be appreciated.
Rachel Bird
En
Hi,
Thanks for testing. Indeed, the HttpServletRequestWrapper is a good
solution.
Would you mind opening a Github issue to track this bug ? I will fix it for
4.1.
Thanks.
Best regards,
Jérôme LELEU
Founder of CAS in the cloud: www.casinthecloud.com | Twitter: @leleuj
Chairman of CAS: www.jasi
Hi Jérôme,
I wasn’t able to restore "service" as a query parameter. For security reasons,
the HttpServletRequest class does not expose any methods to modify its query
parameters .
I’m not sure if there’s a better way, but what I ended up doing was writing a
“Filter” that wraps the request in
Hi,I have a problem with cas 4 and the connector LDAP.I think that i can pass the ldap authentication but the PolicyAuthentication Manager don’t let me pass.I have seen a post here (https://groups.google.com/forum/#!msg/jasig-cas-dev/3CyO92Vk8XA/V2RrUs3m4e8J) which say that to resolved my problem i
Hi Patrick,
If anything, I'd try to do this manually... The default
deployerConfigContext.xml file contains the InMemoryServiceRegistryDaoImpl
registry. It expects to use the fixed defined services that are defined as part
of its own definition (in the 'registeredServices' property).
There is
My suspect was the password encoder mis config, etc. Just for completeness,
would you post the jdbc authn handler bean config?
Cheers,
D.
Sent from my iPhone
> On Jul 16, 2014, at 22:11, "jason" wrote:
>
> Hi Dmitriy,
>
> Thanks for the reply.
>
> Passwords are stored in the db as plain tex
Hi,
I don't remember how I came to test *RequestContextUtil.getTheme*, but
you're right, the default *ServiceThemeResolver* is based on the "service"
query parameter and not on the "service" in the webflow.
Would you mind overriding my OAuthAction with a new one restoring the
"service" as a query
11 matches
Mail list logo