All,
Thanks for the reply. I took the advice and moved to 4.1, however when I
try to access the REST url, using the setup described in documentation, I
get an 302 redirect to the standard login page. Any ideas as to how to
resolve it?
Thanks,
Paul
On Wed, Apr 22, 2015 at 5:25 PM, Dmitriy
Can you send the link to the documentation that you used?
D.
On Apr 23, 2015, at 10:18 AM, Paul Brzek prbag...@gmail.com wrote:
All,
Thanks for the reply. I took the advice and moved to 4.1, however when I try
to access the REST url, using the setup described in documentation, I get an
Hi all!
I’m evaluating CAS, trying to get it hooked up to my users database which lives
on aws.
I’m using
https://github.com/Jasig/cas/wiki/Configuring-Authentication-Components as the
primary docs to help me with this – please let me know if there’s something
better out there. In
See
http://jasig.github.io/cas/development/installation/Configuring-Principal-Resolution.html#principalresolver-vs-authenticationhandler
From: Christopher Myers [mailto:cmy...@mail.millikin.edu]
Sent: Thursday, April 23, 2015 7:41 AM
To: cas-user@lists.jasig.org
Subject: Re: [cas-user]
If that works, that would be awesome! I fought with trying to make that
type of thing work for about two days, but all the Google hits I came
across said that it wasn't possible without using something like that
third-party add-on I'd found.
I didn't try what you suggested though, so if Borys
I added the following in deployerConfigContext.xml,
bean id=loginThrottle
class=org.jasig.cas.web.support.InspektrThrottledSubmissionByIpAddressAndUsernameHandlerInterceptorAdapter
c:auditTrailManager-ref=auditTrailManager
c:dataSource-ref=dataSource
Borys,
Since you are on CAS 3.5.3, you want to configure a separate attribute
repository instead. None of the handlers in CAS 3.5 are able to resolve and
retrieve attributes. See https://wiki.jasig.org/display/CASUM/Attributes
From: Christopher Myers [mailto:cmy...@mail.millikin.edu]
Sent:
Hello Chris,
We use RHEL and mod_auth_cas but use 1 of these 2 approaches to accomplish this
(both with Satisfy any):
SetEnvIf directive
Files directive (or FilesMatch for multiple files)
After your CAS auth directives (in either .htaccess or main apache config):
SetEnvIf Request_URI
Gentlemen,
Was there a problem using CAS 3.5.2 and mod_authnz_ldap?
Thank You,
Chris Cheltenham
SwainTechs / HHS
Cell# 267-586-2369
From: Paul Brzek [mailto:prbag...@gmail.com]
Sent: Thursday, April 23, 2015 10:18 AM
To: cas-user@lists.jasig.org
Subject: Re: [cas-user] CAS 4.0.1 Restful
Neil,
This is what I did on mod_auth_cas.
However , this allows everyone in with a challenge.
I cannot use .htaccess because we have to encrypt all passwords, internal or
not.
Location /var/www/html
SetEnvIf Request_URI (/var/www/html/index.php) allow
Authtype CAS
require valid-user
I didn't follow all of this thread, but if I understand you correctly,
it is possible to do the authentication and pull out the attributes in
one call to ldap. I'm doing this with CAS version 4.0.x.
The key is to configure the principalAttributeMap property in the
ldapAuthenticationHandler bean,
Here you go:
http://jasig.github.io/cas/4.0.x/installation/LDAP-Authentication.html#pri
ncipalresolver-vs-authenticationhandler
From: Christopher Myers [mailto:cmy...@mail.millikin.edu]
Sent: Thursday, April 23, 2015 9:49 AM
To: cas-user@lists.jasig.org
Subject: RE: [cas-user] Fetching LDAP
Hi Chris,
I'm not positive but I think your request_URI is the relative to the path
defined in the directive (and part of the HTTP request), so it should be
something like this:
SetEnvIf Request_URI (/index\.php) allow
We only use this in Directory directives also - I've not tested in
Misagh Moayyed mmoay...@unicon.net 04/23/15 11:57 AM
Here you go:
http://jasig.github.io/cas/4.0.x/installation/LDAP-Authentication.html#principalresolver-vs-authenticationhandler
Awesome, thanks!
Out of random curiosity, is the general policy that the development
documentation isn't
I didn't try what you suggested though, so if Borys would want to try it
out and let us all know, that could save folks a ton of time in the
future too, especially if we could get the change documented on the
github pages :D
Well, all I got was java.lang.NullPointerException :) Probably it
It is a mixed bag. It is definitely supposed to work against the latest
code and SNAPSHOT releases, but it may not work against the actual
release. It depends on what you're after.
Generally, our release policy is that for a minor release such as 4.1, etc
you may experience some differences
Neil,
I appreciate it. So you explicitly protect every page , dir or not?
Thank You,
Chris Cheltenham
SwainTechs / HHS
Cell# 267-586-2369
From: Neil Sabol [mailto:nssa...@unm.edu]
Sent: Thursday, April 23, 2015 11:20 AM
To: cas-user@lists.jasig.org
Subject: RE:[cas-user] mod_auth_cas
Ok cool, good to know, thank you :) I'll keep that in mind for future
upgrades :o)
Misagh Moayyed mmoay...@unicon.net 04/23/15 12:30 PM
It is a mixed bag. It is definitely supposed to work against the latest
code and SNAPSHOT releases, but it may not work against the actual
release. It
From: Christopher Myers
Sent: Thursday, April 23, 2015 6:31 AM
For the Java CAS stuff, you may want to check out the sample webapp
provided here: https://wiki.jasig.org/display/CASC/JA-
SIG+Java+Client+Simple+WebApp+Sample - it gives you a really good, simple
overview of how stuff is set
I had pretty much the same thing written up… (good to know I’m on the right
track!) at least for the affect of the “org.ldaptive.DefaultConnectionFactory”
based bean. This did not work.
I should mention that I’m running CAS 4.0.0. Is your posted solution expected
to work on this version?
--
From: Waldbieser, Carl
Sent: Thursday, April 23, 2015 6:20 AM
We are using mod_auth_cas in front of a couple web apps, and it works pretty
much as you would expect. Since it is a fairly decoupled integration with
your
web app, the log out links in your web app will tend not to work the
Neil,
I am sorry; it is directory not location.
Does this look right?
It's just not working for me.
Directory /var/www/html/new-web
SetEnvIf request_uri /index\.php$ allow
Options +IncludesNoExec
SSLOptions +StdEnvVars
IfModule mod_auth_cas.c
AuthType CAS
AuthName
On Thu, 23 Apr 2015, Paul B. Henson wrote:
From: Waldbieser, Carl
Sent: Thursday, April 23, 2015 6:20 AM
We are using mod_auth_cas in front of a couple web apps, and it works pretty
much as you would expect. Since it is a fairly decoupled integration with your
web app, the log out links in
Looks like you are missing the following:
Allow from env=allow
I believe it should look something like this:
Directory /var/www/html/new-web
SetEnvIf request_uri /index\.php$ allow
Options +IncludesNoExec
SSLOptions +StdEnvVars
IfModule mod_auth_cas.c
AuthType CAS
Misagh Moayyed mmoay...@unicon.net 04/23/15 10:52 AM
See
http://jasig.github.io/cas/development/installation/Configuring-Principal-Resolution.html#principalresolver-vs-authenticationhandler
I guess that's part of my frustration with the new documentation pages -
this is under the
If I had to guess, I would assume that it's because the initial
connection retrieves the attributes that can be potentially passed back
as
the user ID value for the services? So for us this chunk of code looks
like:
bean id=ldapAuthenticationHandler
But I guess if you were using database for auth and ldap for
attrs, then this would be necessary to have separated out.
I think you're right. But I believe that the most common scenario is using
one source for both authentication and attributes. Separation should be an
option, not the
Hi,
As this is my first post here: welcome everyone!
I have a problem with CAS 3.5.3. We are authenticating against two LDAP
servers, our own and external. The second one has very strict access
policy and we can't change its configuration. User can access only his
attributes, nothing else, even
For the Java CAS stuff, you may want to check out the sample webapp provided
here:
https://wiki.jasig.org/display/CASC/JA-SIG+Java+Client+Simple+WebApp+Sample -
it gives you a really good, simple overview of how stuff is set up.
I can't speak to the other CAS clients at the moment however.
You may want to check out this project:
https://github.com/robertoschwald/jasig-cas-examples-robertoschwald
Basically, when CAS validates a users' login attempt, it tends to pull
attributes at that time if so configured. Then, for whatever reason, it
does a subsequent request to pull all of the
Hi,
You may want to check out this project:
https://github.com/robertoschwald/jasig-cas-examples-robertoschwald
Thanks, looks interesting and probably will help. I'll give it a try.
Why CAS is pulling attributes twice? This doesn't make sense.
If you have the alternative of being able to
On Thu, Apr 23, 2015 at 02:37:47PM -0700, Andrew Morgan wrote:
I have several Perl apps that I wanted to CASify. I looked at a few of
the Perl modules for CAS and didn't like what I saw, so I used
mod_auth_cas instead. I'm very happy with mod_auth_cas. It's very easy
to check
32 matches
Mail list logo
