I'm curious if we're able to launch Account Registration from an external link,
for instance we send a user a link to sign up for an account instead of the
user browsing to the login page?
Thanks,
-Jeremy
Jeremy Wickham
Mississippi State University
I am currently developing a mobile application for our university. Right now, I
have implemented authentication using the OAuth2 protocol to take advantage of
the use of the refresh token to limit the user having to log into the app. My
question is once a user has successfully logged via the
I am looking to go to production with v6.2.8 very soon and I am seeing the
following log file when I am starting up.
WARN [com.hazelcast.cp.CPSubsystem] - <[130.18.50.51]:5701 [dev] [4.0.1] CP
Subsystem is not enabled. CP data structures will operate in UNSAFE mode!
Please note that UNSAFE mode
I am looking upgrade our CAS environment to 6.1.x and I am currently ironing
out all of my errors/warnings. There is one warning I'm receiving
WARN [org.springframework.http.converter.json.Jackson2ObjectMapperBuilder] -
Is this something I should be concerned about? I see this warning on
/will create very large logs
depending on your load.
On Thu, Mar 9, 2017 at 1:44 PM, Wickham, Jeremy
<jeremy.wick...@msstate.edu<mailto:jeremy.wick...@msstate.edu>> wrote:
Yes I am using an external tomcat instance. I am also using the CAS overlay
project because I had some c
log
levels for both CAS and Tomcat and see what might be happening. I’d also try
the embedded tomcat and see if that shows the same thing.
--
Misagh
From: Wickham, Jeremy
<jeremy.wick...@msstate.edu><mailto:jeremy.wick...@msstate.edu>
Reply: cas-user@apereo.org<mailto:cas-user@ap
Hazelcast seems to be doing great with CAS. We are also working on getting this
working.
On Mon, Mar 6, 2017 at 2:30 PM, Wickham, Jeremy
<jeremy.wick...@msstate.edu<mailto:jeremy.wick...@msstate.edu>> wrote:
We have been users of the Memcached Ticket Registry for a few years now
(Curren
We have been users of the Memcached Ticket Registry for a few years now
(Current Production CAS is v4.0.4). I am currently looking to upgrade our CAS
implementation to v5.0.x and when implementing the memcached registry in my
test environment, I am getting a lot of inconsistences that do not
Have a question about attributes released to the client. My service definition
has ReturnedAllowedAttributeReleasePolicy, but my logs are telling me that
ReturnAllAttributeReleasePolicy is being used. Is something cached somewhere
that I am unaware of? I've restarted both of my development CAS
Here is the scenario, the service ticket is being created on cas-devel03, and
when cas-devel02 goes to validate, it fails on validation. I am using this
ticket registry in production right now with CAS v4.0.4 is why I am sticking
with memcached.
Here is some data--
CAS v5.0.2
Also when I just have one URL listed for the property, I am receiving an error
that it is trying to connect to localhost:389.
From: cas-user@apereo.org [mailto:cas-user@apereo.org] On Behalf Of Wickham,
Jeremy
Sent: Wednesday, February 08, 2017 11:11 AM
To: cas-user@apereo.org
Subject: [cas
In the CAS Configuration Properties documentation I see:
cas.serviceRegistry.ldap.ldapUrl=ldaps://ldap1.example.edu,ldaps://ldap2.example.edu,...
Currently my setting is -
cas.serviceRegistry.ldap.ldapUrl=ldap://cas-devel.its.msstate.edu,ldap://cas-devel02.its.msstate.edu
With this setting I
It is uid. And yes I set the prinicipalAttributeId with the following config in
the cas.properties
cas.authn.ldap[0].principalAttributeId=uid
Now I see in the docs where I can use the principalAttributeList instead of
cas.authn.attributeRepository.attributes. I tried that it worked like a
I am implementing our login policies into CAS v5.0.2 using the Acceptable Use
Policy module as my guide. We have multiple policies, so I am unable to use AUP
for what we need to accomplish. I'm having an issue retrieving the principal
attributes.
I was hopig someone could guide me on to where
In our current version of CAS (v4.0.4), I have extensively modified the login
web flow. Looking at upgrading to v5.0.1 to implement the duo module, but
before I can get to implementing duo, I need to put our modifications into a
build of v5.0.1.
Just a quick background; the way I have
15 matches
Mail list logo