Excellent. I've re-opened this issue to consider Paul's enhancement.
On Wed, Oct 23, 2013 at 12:48 PM, Paul B. Henson wrote:
>> From: William G. Thompson, Jr. [mailto:wgt...@gmail.com]
>> Sent: Tuesday, October 22, 2013 9:18 AM
>>
>> Sorry I was clearer...the pointer to CAS-1283 was a more of a
> From: William G. Thompson, Jr. [mailto:wgt...@gmail.com]
> Sent: Tuesday, October 22, 2013 9:18 AM
>
> Sorry I was clearer...the pointer to CAS-1283 was a more of a
> suggestion to engage on that ticket...presumably to incorporate your
> enhancements.
Ah, okay; I updated the ticket with a commen
Sorry I was clearer...the pointer to CAS-1283 was a more of a
suggestion to engage on that ticket...presumably to incorporate your
enhancements.
Best,
Bill
On Fri, Oct 11, 2013 at 10:02 PM, Paul B. Henson wrote:
>> From: William G. Thompson, Jr. [mailto:wgt...@gmail.com]
>> Sent: Friday, Octobe
Hi folks,
Just my 2 cents :
With my experience it's really easy to share user attributes over SAML
than with the jsp, why ? until now each CAS deployer tried to use the
jsp to share user attributes but every one made his jsp code and so
there is a lot of schema attributes sharing over this me
> From: William G. Thompson, Jr. [mailto:wgt...@gmail.com]
> Sent: Friday, October 11, 2013 5:36 PM
>
> You'll want to take a look at this: https://issues.jasig.org/browse/CAS-1283
That code looks suspiciously similar to the code on the wiki; I don't really
see how that would not also flatten ou
And this one: https://issues.jasig.org/browse/CAS-1284
On Fri, Oct 11, 2013 at 8:36 PM, William G. Thompson, Jr.
wrote:
> You'll want to take a look at this: https://issues.jasig.org/browse/CAS-1283
>
> Best,
> Bill
>
>
> On Fri, Oct 11, 2013 at 8:16 PM, Paul B. Henson wrote:
>>> From: Marvin
You'll want to take a look at this: https://issues.jasig.org/browse/CAS-1283
Best,
Bill
On Fri, Oct 11, 2013 at 8:16 PM, Paul B. Henson wrote:
>> From: Marvin Addison [mailto:marvin.addi...@gmail.com]
>> Sent: Friday, October 11, 2013 1:40 PM
>>
>> Missed that. That JSP code absolutely will no
> From: Marvin Addison [mailto:marvin.addi...@gmail.com]
> Sent: Friday, October 11, 2013 1:40 PM
>
> Missed that. That JSP code absolutely will not work with the attribute
> parsing code in phpCAS HEAD revision. Here's the source for the
That's an annoying inconsistency, given that piece of the w
On 10/11/2013 01:21 PM, Paul B. Henson wrote:
> No, I meant the post containing the underlying jsp code that generated it:
>
>
>
> ${fn:escapeXml(attr.value)}
>
>
> This code does appear to generate one entry for each attribute, containing
> whatever attr.value is. My curiosity is whe
> No, I meant the post containing the underlying jsp code that generated it:
>
>
>
> ${fn:escapeXml(attr.value)}
>
Missed that. That JSP code absolutely will not work with the attribute
parsing code in phpCAS HEAD revision. Here's the source for the
parsing code [1]:
/**
* Thi
> I understand you to mean /cas/samlValidate here rather than "SAML",
That's exactly what I meant. Only with respect to attribute release in CAS.
M
--
You are currently subscribed to cas-user@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see
On Fri, Oct 11, 2013 at 2:08 PM, Marvin S. Addison
wrote:
>> Hmm, that's the impression I got after a meeting with Unicon, perhaps
>> I misunderstood them.
>
>
> I believe Unicon steers folks away from SAML.
I understand you to mean /cas/samlValidate here rather than "SAML",
but just to be clear,
> From: William G. Thompson, Jr. [mailto:wgt...@gmail.com]
> Sent: Friday, October 11, 2013 11:51 AM
>
> Since you brought up the Unicon meeting I figure I'll just respond
> here in this thread. Sorry if I gave you the wrong impression
> regarding the official status of /cas/samlValidate.
Possib
> The point I was making was that /cas/samlValidate was essentially
> superseded by the 3.0 protocol spec rev (and the CAS 4.0 release) that
> was catching up to broader community practice regarding releasing
> attributes in /cas/serviceValidate.
I would say we're planning to support _both_ the ex
> From: Marvin S. Addison [mailto:marvin.addi...@gmail.com]
> Sent: Friday, October 11, 2013 11:08 AM
>
> You mean this:
>
>
>[a, b,
> c]
>
No, I meant the post containing the underlying jsp code that generated it:
${fn:escapeXml(attr.value)}
This code does appear to generate o
Hey Paul,
Since you brought up the Unicon meeting I figure I'll just respond
here in this thread. Sorry if I gave you the wrong impression
regarding the official status of /cas/samlValidate.
The point I was making was that /cas/samlValidate was essentially
superseded by the 3.0 protocol spec re
Hmm, that's the impression I got after a meeting with Unicon, perhaps
I misunderstood them.
I believe Unicon steers folks away from SAML. I believe it's motivated
in some cases by the need to support proxying with attribute release,
which SAML 1.1 does not support. If they used the word "depre
> From: Marvin S. Addison [mailto:marvin.addi...@gmail.com]
> Sent: Friday, October 11, 2013 6:35 AM
>
> Absolutely not. It may be deprecated at some (distant) future date, but
> many folks are happily using the SAML support in many clients for
> attribute release. No server or client customization
My understanding was that despite it being the "official" mechanism,
SAML is for the most part deprecated
Absolutely not. It may be deprecated at some (distant) future date, but
many folks are happily using the SAML support in many clients for
attribute release. No server or client customization
> From: Tom Poage [mailto:tfpo...@ucdavis.edu]
> Sent: Thursday, October 10, 2013 8:30 AM
>
> The attribute string "[ foo, bar, baz ]" looks suspiciously like the result
> of a
> toString() on a collection.
The jsp code on the wiki:
${fn:escapeXml(attr.value)}
does look like it prett
> From: Marvin S. Addison [mailto:marvin.addi...@gmail.com]
> Sent: Thursday, October 10, 2013 6:18 AM
>
> I honestly don't know. The official mechanism for attribute release is
> via the SAML 1.1 protocol. Attribute release will be officially
> supported in the CAS 3.0 protocol spec:
My understan
On Oct 10, 2013, at 6:18 AM, Marvin S. Addison wrote:
>> What is the "unofficial official" way of handling attributes in the CAS 2.0
>> protocol?
>
> I honestly don't know. The official mechanism for attribute release is via
> the SAML 1.1 protocol. Attribute release will be officially supporte
What is the "unofficial official" way of handling attributes in the CAS 2.0
protocol?
I honestly don't know. The official mechanism for attribute release is
via the SAML 1.1 protocol. Attribute release will be officially
supported in the CAS 3.0 protocol spec:
https://github.com/Jasig/cas/b
23 matches
Mail list logo
