RE:[cas-user] Releasing attributes based upon the service URL

Thanks Misagh, that makes sense. I've got it working now. Regards, Richard -- You are currently subscribed to cas-user@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user

[cas-user] Releasing attributes based upon the service URL

Hi, I've a working instance of CAS that successfully returns certain attributes to any service that uses it. I now want to start returning attributes selectively based upon the service URL. I've duplicated the (sole) RegexRegisteredService bean in my deployerConfigContext.xml file, modifying

RE: [cas-user] Java-sourced custom attributes not being released

u are not getting those two, up the CAS logging to DEBUG and see what's coming out. -Original Message- From: Richard Wiseman [mailto:richard.wise...@bt.com] Sent: Wednesday, August 6, 2014 12:58 AM To: cas-user@lists.jasig.org<mailto:cas-user@lists.jasig.org> Subject: R

RE: [cas-user] Java-sourced custom attributes not being released

ou are not getting those two, up the CAS logging to DEBUG and see what's coming out. -Original Message- From: Richard Wiseman [mailto:richard.wise...@bt.com] Sent: Wednesday, August 6, 2014 12:58 AM To: cas-user@lists.jasig.org<mailto:cas-user@lists.jasig.org> Subject: RE:[cas-user

RE: [cas-user] Java-sourced custom attributes not being released

tributes, two of which can be released. (if you want the handler to take precedence, null out the resolver) If you are not getting those two, up the CAS logging to DEBUG and see what's coming out. -Original Message- From: Richard Wiseman [mailto:richard.wise...@bt.com

RE: [cas-user] Java-sourced custom attributes not being released

two of which can be released. (if you want the handler to take precedence, null out the resolver) If you are not getting those two, up the CAS logging to DEBUG and see what's coming out. -Original Message- From: Richard Wiseman [mailto:richard.wise...@bt.com] Sent: Wednesday, A

RE: [cas-user] Java-sourced custom attributes not being released

ut the resolver) If you are not getting those two, up the CAS logging to DEBUG and see what's coming out. -----Original Message- From: Richard Wiseman [mailto:richard.wise...@bt.com] Sent: Wednesday, August 6, 2014 12:58 AM To: cas-user@lists.jasig.org Subject: RE:[cas-user] Java-sourced cu

RE: [cas-user] Java-sourced custom attributes not being released

be released. (if you want the handler to take precedence, null out the resolver) If you are not getting those two, up the CAS logging to DEBUG and see what's coming out. -----Original Message- From: Richard Wiseman [mailto:richard.wise...@bt.com] Sent: Wednesday, August 6, 2014 12:58 AM

RE:[cas-user] Java-sourced custom attributes not being released

There are lots of commented-out elements from my various attempts and I've scrubbed out the database details but here it is. Thanks! -- You are currently subscribed to cas-user@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-si

RE:[cas-user] Java-sourced custom attributes not being released

Thanks Misagh. I've made some changes and now, just to be explicit, my authenticateUsernamePasswordInternal method ends: Map attributes = new HashMap(); if (billingAccountID != null) attributes.put("billingAccountId", billingAccountID); attributes.put("groupMembership", "GROUP MEMBERSHIP INFORM

[cas-user] Java-sourced custom attributes not being released

This is probably a simple configuration problem, but I have been searching around for ages and can't find out what I've done wrong! I've got some Java that checks user credentials in a custom way (they're stored in a database but I don't think that's relevant). My class extends AbstractJdbcUse

[cas-user] Logout redirects

Hi, Can I specify a delay before a logout redirect takes place? I couldn't see anything in the configuration of my server. The reason I ask is that it redirects to the service URL apparently before CAS has had a chance to post the logout XML to the application, so when the redirect completes

RE: [cas-user] Using SHA512

The password and salt are indeed stored in the same database in different columns. The only encoding I ever seem to see is base64, so the hex actually surprised me! (I've next to no experience with hashing passwords, but my googling has tended to yield results that base64-encode hashes and sal

RE: [cas-user] Using SHA512

Hi Marvin, My database is actually someone else's database, but I do know (now) that the hashes stored in the database are generated using Apache Shiro and that the salt is stored as hex. An example hash is: 4d8d39a8283a53aeb51061457edc32c6a8e5404864b7571bf7b33d2c3bd5c580869ac1635be0d8ee57581f

RE: [cas-user] Using SHA512

mn? Thanks again, Richard From: Dmitriy Kopylenko [mailto:dkopyle...@unicon.net] Sent: 10 July 2014 16:12 To: cas-user@lists.jasig.org<mailto:cas-user@lists.jasig.org> Subject: Re: [cas-user] Using SHA512 Hi Richard. Try SHA-512 instead of SHA512 Best, Dmitriy. On Jul 10, 2014, at 10:04

RE: [cas-user] Using SHA512

@lists.jasig.org<mailto:cas-user@lists.jasig.org> Subject: Re: [cas-user] Using SHA512 Hi Richard. Try SHA-512 instead of SHA512 Best, Dmitriy. On Jul 10, 2014, at 10:04 AM, Richard Wiseman mailto:richard.wise...@bt.com>> wrote: Hi, The CAS documentation <https://wiki.jasig.org/display/CAS

RE: [cas-user] Using SHA512

@lists.jasig.org Subject: Re: [cas-user] Using SHA512 Hi Richard. Try SHA-512 instead of SHA512 Best, Dmitriy. On Jul 10, 2014, at 10:04 AM, Richard Wiseman mailto:richard.wise...@bt.com>> wrote: Hi, The CAS documentation <https://wiki.jasig.org/display/CASUM/JDBC> indicates that you can us

[cas-user] Using SHA512

Hi, The CAS documentation indicates that you can use any of the MACs listed on the JDK Javadoc for the password encoder's encodingAlgorithm attribute; this list in