Re: [cas-user] http error 407 issue
Thanks Jerome but the problem is that I can't understand where I need Proxy autenthication and why! I mean: I access the app with spring plugin with my browser and it's local, the app redirects me to CAS (deployed on the same server) and then CAS posts back with the security ticket on the first path. I miss who needs proxy autenthication in this process...I'm going mad! Il Mercoledì 11 Giugno 2014 8:00, Jérôme LELEU lel...@gmail.com ha scritto: Hi, The HTTP 407 code means that you need some authorization for a proxy: http://www.checkupdown.com/status/E407.html. Does it help? Thanks. Best regards, Jérôme LELEU Founder of CAS in the cloud: www.casinthecloud.com | Twitter: @leleuj Chairman of CAS: www.jasig.org/cas | Creator of pac4j: www.pac4j.org 2014-06-10 15:37 GMT+02:00 MrCrowley mrcrowley...@yahoo.it: Hi there, I have CAS 3.4.3 working in production envirovment within a cluster and apache as webserver in front of Websphere 6.1. Now for some reasons I have to put two application on a development environment which for a lot of reasons is quite different. Basically I have the CAS war and myApplication.The two are deployed on same WAS 6.1 singlenode. Keep in mind I use spring security in the app and I want to go in plain HTTP for now. So when I request a protected URL in myApplication I'm correctly redirected to CAS webapp, I go through the login process and I'm granted a ticket, but when I close the trip with the request back to myAPP with the ticket i get this exception: 2014-06-10 15:24:04,429 INFO [org.jasig.cas.authentication.AuthenticationManagerImpl] - AuthenticationHandler: org.jasig.cas.adaptors.jdbc.QueryDatabaseAuthenticationHandler successfully authenticated the user which provided the following credentials: [username: usrname] [10/06/14 15:24:04:444 CEST] 0501 SystemOut O 2014-06-10 15:24:04,429 INFO [org.jasig.cas.CentralAuthenticationServiceImpl] - Granted service ticket [ST-2-LY6mdKFA4RODJUo0WLH2-cas] for service [http://theserver:9080/myApplication/j_spring_cas_security_check] for user [usrname] [10/06/14 15:24:04:476 CEST] 0501 Cas20ServiceT E org.jasig.cas.client.validation.AbstractCasProtocolUrlBasedTicketValidator retrieveResponseFromServer java.io.IOException: Server returned HTTP response code: 407 for URL: http://theserver:9080/CAS/serviceValidate?service=http%3A%2F%2Ftheserver%3A9080%myApplication%2Fj_spring_cas_security_checkticket=ST-2-LY6mdKFA4RODJUo0WLH2-cas; java.io.IOException: Server returned HTTP response code: 407 for URL: http://theserver:9080/CAS/serviceValidate?service=http%3A%2F%2Ftheserver%3A9080%2FmyApplication%2Fj_spring_cas_security_checkticket=ST-2-LY6mdKFA4RODJUo0WLH2-cas; at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1179) at org.jasig.cas.client.validation.AbstractCasProtocolUrlBasedTicketValidator.retrieveResponseFromServer(AbstractCasProtocolUrlBasedTicketValidator.java:35) at org.jasig.cas.client.validation.AbstractUrlBasedTicketValidator.validate(AbstractUrlBasedTicketValidator.java:178) at org.springframework.security.cas.authentication.CasAuthenticationProvider.authenticateNow(CasAuthenticationProvider.java:131) at org.springframework.security.cas.authentication.CasAuthenticationProvider.authenticate(CasAuthenticationProvider.java:117) at org.springframework.security.authentication.ProviderManager.doAuthentication(ProviderManager.java:130) at org.springframework.security.authentication.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:48) at org.springframework.security.cas.web.CasAuthenticationFilter.attemptAuthentication(CasAuthenticationFilter.java:111) at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(Abs Any IDEAS?I'm going crazy! Thanks a lot -- You are currently subscribed to cas-user@lists.jasig.org as: lel...@gmail.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to cas-user@lists.jasig.org as: mrcrowley...@yahoo.it To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user -- 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
Re: [cas-user] How to integrate jCaptcha with CAS 4.0.0
Hi Chitra ! Do you have any luck integrating JCaptcha with CAS 4 ? If so please inform the steps to accomplish. Thanks in advance, Sunil -- 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
Re: [cas-user] CAS 4.0 : Apache LDAP authentication
Daniel,
Please refer this thread for my working copy of deployerConfigContext.xml
Thanks,
Daniel
On Thursday, June 12, 2014 2:17:26 AM UTC+5:30, Daniel Salzedo wrote:
Sunil,
I am trying to do the same thing with CAS 4.0 in a lab environment. Any
chance of you posting your steps and deployer.Config.Context.xml file?
Thanks!
Daniel.
On Tuesday, June 3, 2014 10:51:40 AM UTC-7, Sunil Kalahasti wrote:
Thanks for your information Bob.
I have succeeded on integrating LDAP with CAS 4.0 some time back. I have
used LDAP Supporting Direct Bind configuration without SSL and pooling.
I would post the steps soon.
Thanks,
Sunil
On Tuesday, June 3, 2014 11:13:06 PM UTC+5:30, Lapanja, Bob@POST wrote:
I recently migrated to CAS 4.0 using LDAP. I didn’t need nor use the
sslConfig attribute or bean. As for the search filter, the documentation
uses {user} instead of %u. That’s also what I used and it worked.
The only places I deviated from the documentation you linked to (for the
LDAP Requiring Authenticated Search section) were:
1) I didn’t use sslConfig
2) I had to set subtreeSearch to true on my
org.ldaptive.auth.PooledSearchDnResolver
3) Some of the properties in the xml config don’t match the properties
file below (e.g. ${ldap.managerDn} and ${ldap.managerPassword} in the xml,
but ${ldap.authn.managerDN} and ${ldap.authn.managerPassword} in the
properties file), so I had to verify those were all named the same thing.
4) I had to add an org.ldaptive.auth.SearchEntryResolver to
org.ldaptive.auth.Authenticator to handle objectGuid.
5) changed %u to {user} in my search filter.
If we do not have ssl connection for ldap, is the following config
necessary:
bean id=connectionConfig class=org.ldaptive.ConnectionConfig
p:ldapUrl=${ldap.url}
p:connectTimeout=${ldap.connectTimeout}
p:useStartTLS=${ldap.useStartTLS}
p:sslConfig-ref=sslConfig/
bean id=sslConfig class=org.ldaptive.ssl.SslConfig
property name=credentialConfig
bean class=org.ldaptive.ssl.X509CredentialConfig
p:trustCertificates=${ldap.trustedCert} /
/property
/bean
Also our ldap parameters were as following:
ldap.userDn=uid=admin,ou=People,o=organization
ldap.search.filter=uid=%u,ou=People,o=organization
ldap.host.name=ldap://as1.organization.com:389
ldap.manager.password=password12345
Do we need any changes in ldap.userDn, ldap.search.filter values for CAS
4.0?
If there is any guide/document related to CAS 4.0 with ldap setup, please
provide reference url.
--
You are currently subscribed to cas-...@lists.jasig.org as:
jasig-cas-user...@googlegroups.com
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
--
You are currently subscribed to cas-...@lists.jasig.org as:
cas-user-ga...@googlegroups.com
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
--
You are currently subscribed to cas-...@lists.jasig.org javascript: as:
cas-user-ga...@googlegroups.com javascript:
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
--
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
Re: [cas-user] CAS 4.0 : Apache LDAP authentication
Daniel,
Please refer this thread for working copy of my deployerConfifContext.xml;:
https://groups.google.com/forum/#!topic/jasig-cas-user/vuQa4ZOuL4U
Thanks,
Sunil
On Thursday, June 12, 2014 2:17:26 AM UTC+5:30, Daniel Salzedo wrote:
Sunil,
I am trying to do the same thing with CAS 4.0 in a lab environment. Any
chance of you posting your steps and deployer.Config.Context.xml file?
Thanks!
Daniel.
On Tuesday, June 3, 2014 10:51:40 AM UTC-7, Sunil Kalahasti wrote:
Thanks for your information Bob.
I have succeeded on integrating LDAP with CAS 4.0 some time back. I have
used LDAP Supporting Direct Bind configuration without SSL and pooling.
I would post the steps soon.
Thanks,
Sunil
On Tuesday, June 3, 2014 11:13:06 PM UTC+5:30, Lapanja, Bob@POST wrote:
I recently migrated to CAS 4.0 using LDAP. I didn’t need nor use the
sslConfig attribute or bean. As for the search filter, the documentation
uses {user} instead of %u. That’s also what I used and it worked.
The only places I deviated from the documentation you linked to (for the
LDAP Requiring Authenticated Search section) were:
1) I didn’t use sslConfig
2) I had to set subtreeSearch to true on my
org.ldaptive.auth.PooledSearchDnResolver
3) Some of the properties in the xml config don’t match the properties
file below (e.g. ${ldap.managerDn} and ${ldap.managerPassword} in the xml,
but ${ldap.authn.managerDN} and ${ldap.authn.managerPassword} in the
properties file), so I had to verify those were all named the same thing.
4) I had to add an org.ldaptive.auth.SearchEntryResolver to
org.ldaptive.auth.Authenticator to handle objectGuid.
5) changed %u to {user} in my search filter.
If we do not have ssl connection for ldap, is the following config
necessary:
bean id=connectionConfig class=org.ldaptive.ConnectionConfig
p:ldapUrl=${ldap.url}
p:connectTimeout=${ldap.connectTimeout}
p:useStartTLS=${ldap.useStartTLS}
p:sslConfig-ref=sslConfig/
bean id=sslConfig class=org.ldaptive.ssl.SslConfig
property name=credentialConfig
bean class=org.ldaptive.ssl.X509CredentialConfig
p:trustCertificates=${ldap.trustedCert} /
/property
/bean
Also our ldap parameters were as following:
ldap.userDn=uid=admin,ou=People,o=organization
ldap.search.filter=uid=%u,ou=People,o=organization
ldap.host.name=ldap://as1.organization.com:389
ldap.manager.password=password12345
Do we need any changes in ldap.userDn, ldap.search.filter values for CAS
4.0?
If there is any guide/document related to CAS 4.0 with ldap setup, please
provide reference url.
--
You are currently subscribed to cas-...@lists.jasig.org as:
jasig-cas-user...@googlegroups.com
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
--
You are currently subscribed to cas-...@lists.jasig.org as:
cas-user-ga...@googlegroups.com
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
--
You are currently subscribed to cas-...@lists.jasig.org javascript: as:
cas-user-ga...@googlegroups.com javascript:
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
--
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
Re: [cas-user] How to integrate jCaptcha with CAS 4.0.0
CAS 3.4 not is compatible with 3.5 and therefore 4 branch. The solution is easier that that link explains and could valid for all versions. When somebody don't know techologies behind frameworks, appears solutions as you had applied in your CAS 3.4. In fact, that AuthenticationViaFormAction patch is not required due to the flexibility of webflows. Have you tried to extend your Credentials bean with the field and use a custom Spring validation annotation? All magic is made transparentily when in your transitions put the validate=true. I will kill the Captcha Servlet and Singleton and use the powerfull of Spring beans describe here http://www.programacionj2ee.com/jcpatcha-con-spring/ to customize your image. TODO: - Code a bean extending from UsernamePasswordCredentials with a property, e.g captcha, and use it as a login flow credentials bean. - Code a Spring Validator that use your captchaService to validate it from request and session id. http://stackoverflow.com/questions/22300968/spring-webflow-model-validation - Map it in the binder to bind it in the view state as (MAGIC!!! That binding line is the only you need to modify in 4.x login-webflow): view-state id=viewLoginForm view=casLoginView model=credentials binder binding property=username / binding property=password / *binding property=captcha /* /binder on-entry set name=viewScope.commandName value='credentials' / /on-entry transition on=submit bind=true validate=true to=realSubmit evaluate expression=authenticationViaFormAction.doBind(flowRequestContext, flowScope.credentials) / /transition !-- CAS Password Manager Transitions -- transition on=forgotPassword to=passwordManager validate= false set name=flashScope.pmTask value='forgotPassword'/ /transition transition on=changePassword to=passwordManager validate= false set name=flashScope.pmTask value='changePassword'/ /transition /view-state 2014-06-16 12:25 GMT+02:00 Sunil Kalahasti sunilkalaha...@gmail.com: Hi Chitra ! Do you have any luck integrating JCaptcha with CAS 4 ? If so please inform the steps to accomplish. Thanks in advance, Sunil -- You are currently subscribed to cas-user@lists.jasig.org as: kate...@gmail.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user -- 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
Re: [cas-user] CAS attributes via SAML not working
Hi, I am still attempting to get CAS to release attributes and not having much luck. My user goes to the the web site, logs in, and gets a 401 http code with the message This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g. bad password), or your browser does't understand how to supply the credentials required. My cas configuration points CASValidateURL to the samlValidate (thank you Andrew Morgan for that tip) target: LoadModule auth_cas_module modules/mod_auth_cas.so IfModule mod_auth_cas.c CASLoginURL https://cas-dev.mines.edu/cas/login CASVersion 2 CASValidateURL https://cas-dev.mines.edu/cas/samlValidate CASValidateSAML On CASCertificatePath /etc/pki/tls/certs/ca-bundle.crt CASCookiePath /var/tmp/cas/ CASSSOEnabled On CASValidateServer On CASAttributePrefix boobooboo CASDebug On /IfModule Grasping at straws, I moved from a server running CentOS 5.10 to one running 6.5. Mostly hoping that the newer version of curl and other libraries would help, but the result is the same. When I use CASValidateURL pointed at https://cas-dev.mines.edu/cas/serviceValidate, the user can log in and see the content, but no attributes. When I use https://cas-dev.mines.edu/cas/samlValidate I get the 401, but the attributes do show up in the debug logs so attributes are getting released, but the session is not getting valided. Here are the debug logs from mod_auth_cas from httpd: [Mon Jun 16 15:45:07 2014] [debug] mod_auth_cas.c(1745): [client 138.67.125.10] Entering cas_authenticate() [Mon Jun 16 15:45:07 2014] [debug] mod_auth_cas.c(519): [client 138.67.125.10] entering getCASService() [Mon Jun 16 15:45:07 2014] [debug] mod_auth_cas.c(539): [client 138.67.125.10] CAS Service 'https%3a%2f%2fw4.mines.edu%2fcastest' [Mon Jun 16 15:45:07 2014] [debug] mod_auth_cas.c(485): [client 138.67.125.10] entering getCASLoginURL() [Mon Jun 16 15:45:07 2014] [debug] mod_auth_cas.c(462): [client 138.67.125.10] entering getCASGateway() [Mon Jun 16 15:45:07 2014] [debug] mod_auth_cas.c(555): [client 138.67.125.10] entering redirectRequest() [Mon Jun 16 15:45:07 2014] [debug] mod_auth_cas.c(567): [client 138.67.125.10] Adding outgoing header: Location: https://cas-dev.mines.edu/cas/login?service=https%3a%2f%2fw4.mines.edu%2fcastest [Mon Jun 16 15:45:20 2014] [debug] mod_auth_cas.c(1745): [client 138.67.125.10] Entering cas_authenticate(), referer: https://cas-dev.mines.edu/cas/login?service=https%3a%2f%2fw4.mines.edu%2fcastest [Mon Jun 16 15:45:20 2014] [debug] mod_auth_cas.c(607): [client 138.67.125.10] Modified r-args (old 'ticket=ST-1-ZNUMSFN4lgafoxDSH5g0-cas-dev.mines.edu', new ''), referer: https://cas-dev.mines.edu/cas/login?service=https%3a%2f%2fw4.mines.edu%2fcastest [Mon Jun 16 15:45:20 2014] [debug] mod_auth_cas.c(1600): [client 138.67.125.10] entering getResponseFromServer(), referer: https://cas-dev.mines.edu/cas/login?service=https%3a%2f%2fw4.mines.edu%2fcastest [Mon Jun 16 15:45:20 2014] [debug] mod_auth_cas.c(519): [client 138.67.125.10] entering getCASService(), referer: https://cas-dev.mines.edu/cas/login?service=https%3a%2f%2fw4.mines.edu%2fcastest [Mon Jun 16 15:45:20 2014] [debug] mod_auth_cas.c(539): [client 138.67.125.10] CAS Service 'https%3a%2f%2fw4.mines.edu%2fcastest', referer: https://cas-dev.mines.edu/cas/login?service=https%3a%2f%2fw4.mines.edu%2fcastest [Mon Jun 16 15:45:21 2014] [debug] mod_auth_cas.c(1674): [client 138.67.125.10] Validation response: ?xml version=1.0 encoding=UTF-8?SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/;SOAP-ENV:Bodysaml1p:Response xmlns:saml1p=urn:oasis:names:tc:SAML:1.0:protocol IssueInstant=2014-06-16T21:45:20.963Z MajorVersion=1 MinorVersion=1 Recipient=https://w4.mines.edu/castest; ResponseID=_4e06e9d9ac93a830cbd92e27e3eb9cd4saml1p:Statussaml1p:StatusCode Value=saml1p:Success//saml1p:Statussaml1:Assertion xmlns:saml1=urn:oasis:names:tc:SAML:1.0:assertion AssertionID=_8a9db6ecf524737797da624df57f5e70 IssueInstant=2014-06-16T21:45:20.963Z Issuer=localhost MajorVersion=1 MinorVersion=1saml1:Conditions NotBefore=2014-06-16T21:45:20.963Z NotOnOrAfter=2014-06-16T21:45:50.963Zsaml1:AudienceRestrictionConditionsaml1:Audiencehttps://w4.mines.edu/castest/saml1:Audience/saml1:AudienceRestrictionCondition/saml1:Conditionssaml1:AuthenticationStatement AuthenticationInstant=2014-06-16T21:45:20.725Z AuthenticationMethod=urn:oasis:names:tc:SAML:1.0:am:unspecifiedsaml1:Subjectsaml1:NameIdentifiertestua/saml1:NameIdentifiersaml1:SubjectConfirmationsaml1:ConfirmationMethodurn:oasis:names:tc:SAML:1.0:cm:artifact/saml1:ConfirmationMethod/saml1:SubjectConfirmation/saml1:Subject/saml1:AuthenticationStatementsaml1:AttributeStatementsaml1:Subjectsaml1:NameIdentifiertestua/saml1:NameIdentifiersaml1:SubjectConfirmationsaml1:ConfirmationMethodurn:oasis:names:tc:SAML:1.0:cm:artifact/saml1:ConfirmationMethod/saml1:SubjectConfirmation/saml1:Subjectsaml1:Attribute
[cas-user] Recommended CAS server/client
(This is another attempt at posting using the Google Group. My last one seems to have been bounced by Wisc. Apologies if this gets posted multiple times somehow.) I'm interested in using CAS with JBoss AS 7. Could someone recommend which combination of server/client I should start with? According to the homepage the latest CAS server is 3.5.2.1, but the mailing list says that 4.0.0 is out. According to the wiki the latest Java client is 3.2.1, but I see 3.3.1 in Maven. Thanks! Tom -- 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
Re:[cas-user] CAS OAuth Support 3.5.2 - Working with service parameter.
The exception I got appears to have been caught and handled by
CAS/OAuthAction. There's not much of a trace in the log.
OAuthAction.doExecute:
.
.
.
} catch (final TicketException e) {
return error();
}
cas.log
2014-06-16 18:07:07,023 INFO
org.jasig.cas.authentication.AuthenticationManagerImpl -
edu.cas.service.implementation.OAuthAuthenticationHandlerImplementation failed
authenticating
org.jasig.cas.support.oauth.authentication.principal.OAuthCredentials@27f34293
cas-authentication.log
2014-06-16 18:08:43,338 INFO Audit trail record BEGIN
=
WHO:
org.jasig.cas.support.oauth.authentication.principal.OAuthCredentials@27f34293
WHAT: error.authentication.credentials.bad.usernameorpassword
ACTION: TICKET_GRANTING_TICKET_NOT_CREATED
APPLICATION: CAS
WHEN: Mon Jun 16 18:08:43 EDT 2014
CLIENT IP ADDRESS: 127.0.0.1
SERVER IP ADDRESS: 127.0.0.1
=
Again, the problem seems to be that when RequestContextUtil.getTheme is
eventually called, the default theme is used because the service parameter is
null.
The following is the comment for the OAuthAction class:
/**
* This class represents an action in the webflow to retrieve OAuth information
on the callback url which is the webflow url (/login). The
* {@link org.jasig.cas.support.oauth.OAuthConstants.OAUTH_PROVIDER} and the
other OAuth parameters are expected after OAuth authentication.
* Providers are defined by configuration. The {@link
org.jasig.cas.support.oauth.OAuthConstants.SERVICE},
* {@link org.jasig.cas.support.oauth.OAuthConstants.THEME}, {@link
org.jasig.cas.support.oauth.OAuthConstants.LOCALE} and
* {@link org.jasig.cas.support.oauth.OAuthConstants.METHOD} parameters are
saved and restored from web session after OAuth authentication.
*
* @author Jerome Leleu
* @since 3.5.0
*/
Is the comment about restoring parameters from the web session referring to the
following code?
// retrieve parameters from web session
final Service service = (Service)
session.getAttribute(OAuthConstants.SERVICE);
context.getFlowScope().put(OAuthConstants.SERVICE, service);
restoreRequestAttribute(request, session, OAuthConstants.THEME);
restoreRequestAttribute(request, session, OAuthConstants.LOCALE);
restoreRequestAttribute(request, session, OAuthConstants.METHOD);
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-sig.org/wiki/display/JSG/cas-user
Re: [cas-user] Recommended CAS server/client
You should use the 4.0.0 release of the server and the 3.3.1 release of the CAS client. And we should update our documentation :-) On Mon, Jun 16, 2014 at 6:34 PM, Tom Arnold tar...@gmail.com wrote: (This is another attempt at posting using the Google Group. My last one seems to have been bounced by Wisc. Apologies if this gets posted multiple times somehow.) I'm interested in using CAS with JBoss AS 7. Could someone recommend which combination of server/client I should start with? According to the homepage the latest CAS server is 3.5.2.1, but the mailing list says that 4.0.0 is out. According to the wiki the latest Java client is 3.2.1, but I see 3.3.1 in Maven. Thanks! Tom -- You are currently subscribed to cas-user@lists.jasig.org as: scott.battag...@gmail.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user -- 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
Re: [cas-user] Recommended CAS server/client
I've updated our www.jasig.org/cas page. Which wiki link was out of date? On Mon, Jun 16, 2014 at 10:06 PM, Scott Battaglia scott.battag...@gmail.com wrote: You should use the 4.0.0 release of the server and the 3.3.1 release of the CAS client. And we should update our documentation :-) On Mon, Jun 16, 2014 at 6:34 PM, Tom Arnold tar...@gmail.com wrote: (This is another attempt at posting using the Google Group. My last one seems to have been bounced by Wisc. Apologies if this gets posted multiple times somehow.) I'm interested in using CAS with JBoss AS 7. Could someone recommend which combination of server/client I should start with? According to the homepage the latest CAS server is 3.5.2.1, but the mailing list says that 4.0.0 is out. According to the wiki the latest Java client is 3.2.1, but I see 3.3.1 in Maven. Thanks! Tom -- You are currently subscribed to cas-user@lists.jasig.org as: scott.battag...@gmail.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user -- 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
