On 25/02/11 16:05, Marvin Addison wrote:
That was it :)))
Whew! Sorry we didn't arrive at that sooner. I see in the thread
that Joachim suggested to look at that pretty early on, but somehow it
got lost in the mix. All's well that ends well, I guess.
I didn't know I had to to click als
On 24/02/11 21:50, Marvin Addison wrote:
Giannis, I apologize this took so long, but I've finally added some
additional server-side logging that I hope will help. See
https://issues.jasig.org/browse/CAS-954. Please grab source from
https://source.jasig.org/cas3/branches/cas-3_4_x_maintenance/ca
Giannis, I apologize this took so long, but I've finally added some
additional server-side logging that I hope will help. See
https://issues.jasig.org/browse/CAS-954. Please grab source from
https://source.jasig.org/cas3/branches/cas-3_4_x_maintenance/cas-server-3.4.2/,
build/deploy, and see if i
On 03/11/10 16:47, Marvin Addison wrote:
>> I'm attaching TRACE log on org.jasig.
> I studied your log carefully and I see nothing that would indicate a
> server problem with attribute release. Quite the contrary, I see all
> the right signs:
>
> 1. The service is recognized and the attributes are
> I'm attaching TRACE log on org.jasig.
I studied your log carefully and I see nothing that would indicate a
server problem with attribute release. Quite the contrary, I see all
the right signs:
1. The service is recognized and the attributes are allowed in the
service registry:
2010-10-30 12:10
> Marvin is there a chance that attributes are not released because
> I have an apache proxy in front of Tomcat?
I doubt that's the problem. I can see from previous posts you're
getting a well-formed SAML response, but it's simply missing
AttributeStatement elements. It's hard to imagine a rever
On 20/10/10 16:35, Marvin Addison wrote
I must admit I'm doubtful the bean naming issue I described above is
preventing attributes from being released, but let's fix that and see
where it gets us.
M
Marvin is there a chance that attributes are not released because
I have an apache proxy in fr
On 20/10/10 16:35, Marvin Addison wrote:
I believe this is wrong. The top-most attribute repository bean must
be called attributeRepository, so you'd want
MergingPersonAttributeDaoImpl to have the name "attributeRepository"
and the delegated attribute repository to have another name. We do
som
> class="org.jasig.services.persondir.support.MergingPersonAttributeDaoImpl">
>
>
>
>
>
I believe this is wrong. The top-most attribute repository bean must
be called attributeRepository, so you'd want
MergingPersonAttributeDaoImpl to have the name "attributeRepository"
and the delegated at
The logs are attached.
It's suspect that the last attribute query entry is the following:
[org.jasig.services.persondir.support.ldap.LdapPersonAttributeDao] -
Generated query builder '(edupersonprincipalname=u...@example.com)'
from query Map {username=[u...@example.com]}.
In the case of succe
On 23/09/10 15:08, Kapetanakis Giannis wrote:
Is there a chance that my pom.xml is causing all this trouble
(maybe something that is needed is not enabled.
I have modified the original pom.xml from cas-server-webapp.
I've attaching my pom.xml
pom.xml was not the problem. I added the original
On 20/09/10 15:58, Marvin Addison wrote:
> Attribute release is supported out of the box using the SAML 1.1
> protocol. I encourage you to avoid customizing
> casServiceValidationSuccess.jsp as you have, which amounts to an
> undocumented extension to the CAS 2.0 protocol. You should only do
On 21/09/10 17:26, Marvin Addison wrote:
The logs are attached.
It's suspect that the last attribute query entry is the following:
[org.jasig.services.persondir.support.ldap.LdapPersonAttributeDao] -
Generated query builder '(edupersonprincipalname=u...@example.com)'
from query Map {username=[
> The logs are attached.
It's suspect that the last attribute query entry is the following:
[org.jasig.services.persondir.support.ldap.LdapPersonAttributeDao] -
Generated query builder '(edupersonprincipalname=u...@example.com)'
from query Map {username=[u...@example.com]}.
In the case of succes
ok, I reverted back to the original casServiceValidationSuccess.jsp
I also enabled DEBUG logging in log4j.xml for org.jasig
The logs are attached.
regards,
Giannis
--
You are currently subscribed to cas-user@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or acces
> I've also fixed casServiceValidationSuccess.jsp according to
> https://issues.jasig.org/browse/CAS-655
Attribute release is supported out of the box using the SAML 1.1
protocol. I encourage you to avoid customizing
casServiceValidationSuccess.jsp as you have, which amounts to an
undocumented ex
The casServiceValidationSuccess.jsp is for the cas2.0 protocol and not
for saml.
Have you allowed the attribute release in the service management gui for
the specific service?
Regards,
Joachim
Am 17.09.2010 12:24, schrieb Kapetanakis Giannis:
I've also fixed casServiceValidationSuccess.jsp
I've also fixed casServiceValidationSuccess.jsp according to
https://issues.jasig.org/browse/CAS-655
${fn:escapeXml(attr.value)}
Also CASClient::setSessionAttributes('http://schemas.xmlsoap.org/soap/envelope/";>http://www.w3.org/2001/XMLSchema";
xmlns:xsi="
Hi,
I have a working setup of cas-server 3.4.2.1 with many services
authenticating
through CAS.
I want to setup a new service with phpCAS 1.1.2 and do attribute release
through SAML 1.1
using an LDAP repo.
I've read
https://wiki.jasig.org/display/CASC/phpCAS+examples#phpCASexamples-SAMLProto
http://www.ja-sig.org/issues/browse/MAS-37
On 2/10/10 3:09 PM, Scott Battaglia wrote:
> I would encourage you to at least open a JIRA issue and attach the patch
> even if you could provide no other assistance.
>
> Thanks!
> Scott
>
>
> On Wed, Feb 10, 2010 at 12:09 PM, David Hawes wrote:
>
>>
I would encourage you to at least open a JIRA issue and attach the patch
even if you could provide no other assistance.
Thanks!
Scott
On Wed, Feb 10, 2010 at 12:09 PM, David Hawes wrote:
> On 2/10/10 11:29 AM, Scott Battaglia wrote:
> > David,
> >
> > Is there a JIRA issue to get this patch in
On 2/10/10 11:29 AM, Scott Battaglia wrote:
> David,
>
> Is there a JIRA issue to get this patch into mod_auth_cas ? (if you want to
> contribute it?)
There is no JIRA issue, but I wouldn't mind contributing it.
It does need more testing. I made it as a proof of concept for a user
about six mon
David,
Is there a JIRA issue to get this patch into mod_auth_cas ? (if you want to
contribute it?)
Thanks
Scott
On Wed, Feb 10, 2010 at 11:21 AM, David Hawes wrote:
> On 2/9/10 6:10 PM, Vitty, Paul wrote:
> ...
> > Secondly, has anyone been able to get SAML release and mod_auth_cas
> > to wor
On 2/9/10 6:10 PM, Vitty, Paul wrote:
...
> Secondly, has anyone been able to get SAML release and mod_auth_cas
> to work successfully, by that I mean .htaccess files with 'require
> group student' etc, where the group information is provided by SAML
> release to mod_auth_cas?
Attached is a patch
Hi,
I'm just working on moving our installation from v3.3.3 to 3.3.5 and have a
couple of questions, which aren't really related to the upgrade specifically.
First, I remember seeing somewhere in the wiki pages about changing the
Attribute repository for release of SAML information from LDAP to
25 matches
Mail list logo
