Re: [cas-user] [cas-announce] CAS v.4.0.3 is released

Hi, There are default values for these placeholders so you shouldn't have any error (${propertyname:defaultvalue}). What's your error? Thanks. Best regards, Jérôme 2015-08-05 6:13 GMT+02:00 Batni, Sourabh : > > -- > *From:* Batni, Sourabh > *Sent:* Tuesday, August 4

[cas-user] [cas-announce] CAS v.4.0.3 is released

From: Batni, Sourabh Sent: Tuesday, August 4, 2015 2:28 PM To: Misagh Moayyed; cas-annou...@lists.ja-sig.org Subject: RE: [cas-announce] CAS v.4.0.3 is released Hi Misagh After I updated the cas.version in pom.xml to 4.0.3 from 4.0.1 the war file failed to deplo

Re: [cas-user] Leading White space in username/netid

Thanks, I’ll test that tomorrow. -Bryan From: Dmitriy Kopylenko mailto:dkopyle...@unicon.net>> Reply-To: "cas-user@lists.jasig.org" mailto:cas-user@lists.jasig.org>> Date: Tuesday, August 4, 2015 at 5:23 PM To: "cas-user@lists.jasig.org

Re: [cas-user] Leading White space in username/netid

https://groups.google.com/forum/m/#!topic/jasig-cas-user/pz-NZH9H7yI Sent from my iPhone > On Aug 4, 2015, at 18:54, Bryan Wooten wrote: > > Hi all, > > Here is the scenario: > > Login into our CASified Peoplesoft with a leading whitespace on the user name. > CAS authenticates against OpenDJ

[cas-user] Leading White space in username/netid

Hi all, Here is the scenario: 1. Login into our CASified Peoplesoft with a leading whitespace on the user name. 2. CAS authenticates against OpenDJ just fine 3. Peoplesoft gets the netid/username with the leading white space in REMOTE_USER (We are using the Wrapper Filter) 4. Peopl

RE: [cas-user] CAS 4 (Unicon overlay) with AD plus attributes

I knew this sounded familiar, and so I dug this up: https://github.com/Jasig/cas/issues/722 Long story short; it’s something that is fixed and will need to be backported to 4.0.4. From: Misagh Moayyed [mailto:mmoay...@unicon.net] Sent: Tuesday, August 4, 2015 11:58 AM To: 'cas-user@lists.ja

Re: [cas-user] CAS 4 (Unicon overlay) with AD plus attributes

I'm glad It's not just me. I was starting to go a little nuts trying everything I could think of. Thanks, Mark From: Kevin Sewell Reply-To: "cas-user@lists.jasig.org" Date: Tuesday, August 4, 2015 at 12:57 PM To: "cas-user@lists.jasig.org

RE: [cas-user] CAS 4 (Unicon overlay) with AD plus attributes

That is the default behavior, yes, supposedly :) You should not get anything unless you explicitly allow them. >From what you’re describing, this sounds like a regression. Please submit an issue, and attach a sample of your deployerConfigFile.xml to the issue. Time permitting, the fix might g

Re: [cas-user] CAS 4 (Unicon overlay) with AD plus attributes

I would think that the default behavior would be to restrict attributes unless released, instead of the reverse. Thanks, Mark From: Kevin Sewell Reply-To: "cas-user@lists.jasig.org" Date: Tuesday, August 4, 2015 at 12:57 PM To: "cas-user@lists.jasig.org

Re: [cas-user] CAS 4 (Unicon overlay) with AD plus attributes

Just reporting that I'm seeing this behaviour too (but didn't play with filters). I was expecting that an empty "allowedAttributes" list with "ignoreAttributes" set to "false" (or not specifying it) to result in no attribute release for that RegexRegisteredService. The logs are telling me that m

Re: [cas-user] CAS 4 (Unicon overlay) with AD plus attributes

OK, I got the attributes released but now I have one more question. We don’t have a need for the Services Manager, we only want to release attributes to one service. I added a RegexRegisteredService to the RegisteredServicesList and this new service has "ingnoreAttributes" set to "true" (releas