Hi Justin,
CAS 5 have said that at least the UI will have problem with IE 9 or below,
so I doubt they build CAS 5 with IE 7 support in mind
https://apereo.github.io/cas/5.3.x/installation/User-Interface-Customization.html#browser-support
I don't have IE 7 setup on my system so can't really test
Hi Travis,
> To remove unwanted authentication attributes add
excludeDefaultAttributes: true.
Oh we can do that?! Didn't knows about that and good to learn about this!
Thanks Travis :)
Cheers!
- Andy
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
Carl,
Do you have saml support enabled:
compile "org.apereo.cas:cas-server-support-saml:${casServerVersion}"
Ray
On Thu, 2020-01-23 at 15:32 -0800, crdaudt wrote:
Here is the entire JSON file (using the real server names, but blanking out the
"memberOf" security groups):
---BEGIN---
{
Here is the entire JSON file (using the real server names, but blanking out
the "memberOf" security groups):
---BEGIN---
{
"@class" : "org.apereo.cas.services.RegexRegisteredService",
"serviceId": "^http(s)?://servicespre\\.taylor(u)?\\.edu(/.*)?$",
"name": "TOWER -- services",
"id":
{
"serviceId": "^http(s)?://our_banner_server\\.taylor(u)?\\.edu(/.*)?$",
"name": "TOWER -- services",
(and so forth)
}
On Thursday, January 23, 2020 at 5:48:01 PM UTC-5, rbon wrote:
>
> Carl,
>
> TARGET is used with SAML 1.1 protocol (which Banner uses), service with
> CAS protocol(s).
>
Hello All,
We are working on upgrading from CAS 3.5.1 to CAS 5.3.7 and so far
everything has gone pretty smoothly, although we have just hit one issue.
We have a very very old .Net application that is end of life and we are
migrating users off of it but that will take a while to do. This app
Carl,
TARGET is used with SAML 1.1 protocol (which Banner uses), service with CAS
protocol(s).
What is your service Id?
It is odd that it works with service= and not TARGET=.
Ray
On Thu, 2020-01-23 at 14:24 -0800, crdaudt wrote:
We have had our Ellucian Banner service authenticating users
We have had our Ellucian Banner service authenticating users through our
CAS 5.2.2 service for several years, and are now attempting to migrate to
our CAS 6.1.3 service. However, CAS does not recognize the JSON entry that
we have in place for Banner. I believe the issue is related to the fact
Hope this is the right place to list CAS Management bugs, there are several
to report.
Please know that I love the tool and wanted to provide detailed feedback.
My management.properties looks like:
cas.server.name=https://casdev-master.hvcc.edu
cas.server.prefix=${cas.server.name}/cas
Filter Chain Debugging...I've poured over the core code, I cannot for
the life of me figure out why the "/login/cas" request is not take the
user to CAS for authentication
This was working before, I have no clue why it isn't know..the
LogOutFilter on "/logout/cas" is working. Anyone have any
I believe I am having the exact same issue, I have the same setup:
CAS 6.1.2 acting as an SP, delegating authentication to Azure AD.
All works fine but I intermittently get an Application is not authorised
error.
With debug enabled I have the same entries in the error log (works when the
Andy,
Awesome! Thank you for the heads up!
Bill
On Thu, Jan 23, 2020 at 1:10 AM Andy Ng wrote:
> Hi Bill,
>
> Seems like the CAS team will be fixing this in latest CAS version, see
> this commit:
>
> https://github.com/apereo/cas/commit/e214dba59c2273409c406cf4301e2dc875183295
>
> Looks to me
Hello,
I have a strange problem after upgrading CAS from 6.0.3 to 6.1.3: I don't
use any *cas.authn.mfa.** properties. Should I add some additional
dependency to my list to fix this exception?
This exception appears after big STOP label in console:
Caused by:
To remove unwanted authentication attributes add excludeDefaultAttributes:
true.
On Thu, Jan 23, 2020 at 7:33 AM Josh wrote:
> Apologies, I see you have that already, I mis-read the original post :)
>
> On Thursday, January 23, 2020 at 10:32:36 AM UTC-5, Josh wrote:
>>
>> You dont need an
Apologies, I see you have that already, I mis-read the original post :)
On Thursday, January 23, 2020 at 10:32:36 AM UTC-5, Josh wrote:
>
> You dont need an allowedAttributes sections for this, just an
> attributeReleasePolicy like so:
>
>attributeReleasePolicy : {
> @class :
You dont need an allowedAttributes sections for this, just an
attributeReleasePolicy like so:
attributeReleasePolicy : {
@class : org.apereo.cas.services.ReturnMappedAttributeReleasePolicy
allowedAttributes : {
@class : java.util.TreeMap
mail :
Hi Andy,
I have tried that so only this in the JSON:
{
"@class" : "org.apereo.cas.support.saml.services.SamlRegisteredService",
"serviceId" : "SERVICE",
"name" : "Apache Secured By SAML",
"id" : 10011,
"description" : "CAS development Apache mod_shib/shibd server with
Hi everyone,
I'm testing the Apache Guacamole solution and i want to set CAS
authentication. I have installed the CAS extension in the Guacamole app in
Tomcat.
When i reach https://guacamole.ourdomain.fr/guacamole, i am correctly
redirected to https://cas.ourdomain.fr/cas/login. I enter my
Hi Jeff,
Have you tried allow all and see if the issue is due to the allowAttribute
or other matter?
Setup allow all as such:
https://apereo.github.io/cas/6.0.x/integration/Attribute-Release-Policies.html#return-all
Cheers!
- Andy
--
- Website: https://apereo.github.io/cas
- Gitter
Hello All,
I am trying to move away from shibboleth IDP and move to CAS IDP but having
a few issues, I have had a look at the documentation and this group and
cannot seem to find the answer. I need to pass certain attributes, these
ones -
urn:oid:0.9.2342.19200300.100.1.3 - mail value email
Update: the service I'm using to send the Signal messages also accepts this
kind of requests:
curl -X POST -d '{"message":"foo"}' http:
//localhost:5000/json/
Here's more details: https://morph027.gitlab.io/signal-web-gateway/usage/
--
- Website: https://apereo.github.io/cas
- Gitter
21 matches
Mail list logo
