So it seems the format string property is not being resolved:
> [org.ldaptive.auth.FormatDnResolver] - Formatting DN for myuser with
> ${ldap.authn.searchFilter}
> [org.ldaptive.auth.Authenticator] - dn=${ldap.authn.searchFilter} with ...
The issue looks to have been identified/covered during e
Your configuration of the DAO likely needs to invoke the init method via
Spring. Tell your bean config to initialize itself via the init-method
attribute.
From: cas-user@apereo.org [mailto:cas-user@apereo.org] On Behalf Of Jonathan
Labin
Sent: Thursday, January 21, 2016 12:41 PM
To: CAS Commu
As follow up, I'm finding that the file containing the JSON attributes
seems to be being ignored. Syntax errors aren't being noticed and I'm not
seeing the log message that the code contains:
Un-marshaling person attributes from the config file
Is something else required for the repository to
seeing in the log file
2016-01-21T17:13:42.241+|Info: 2016-01-21 17:13:42,241 DEBUG
[org.jasig.services.persondir.support.JsonBackedComplexStubPersonAttributeDao]
-
2016-01-21T17:13:42.241+|Info: 2016-01-21 17:13:42,241 DEBUG
[org.jasig.services.persondir.support.JsonBackedComplexStubP
Hi,
Yes, the OAuth server protocol support is a facade which delegates the
authentication process to the CAS server itself.
Thanks.
Best regards,
Jérôme
2016-01-21 11:37 GMT+01:00 Petr Gašparík - AMI Praha a.s. <
petr.gaspa...@ami.cz>:
> Hi,
>
> If I have two applications,
>
>- AppC connec
Hi,
If I have two applications,
- AppC connected to CAS server via CAS client (CAS protocol),
- AppO second connected to CAS server via OAuth protocol,
does the Web SSO work?
Is user logged into AppC automatically logged into AppO?
If not, it is possible to do it in some way?
This s
