Fwd: [cas-user] Issue when using JSON (Whitelist) Authentication with Password Encoding

> > Hi all, > > I have a problem when using JSON Authentication with Password Encoding. > I used both CAS versions 5.3.2 and 5.3.3, and below is the used config: > > *Properties:* > > cas.authn.json.location=file:/path_xx/users-SHA-256.json > #cas.authn.json.name= > cas.authn.json.passwordEncoder

AW: [cas-user] CAS 5.3.x [SAML] + [Attribute Consent] seems not working + my workaround

Hi Andy, I found the same problem migrating from 5.2 to 5.3. For me, the redirect after consent was to {cas.url}/{SAML-Service-ID}. I haven’t looked into it yet, but there might be some confusion evaluating the correct callback endpoint. Notice that after consent, the request will go to the

[cas-user] Re: Disabling Following Referrals in LDAP

I have found this https://support.symantec.com/en_US/article.TECH226886.html for ldap referrel but I didn't find anything to ignore the ldap referel. On Monday, November 19, 2018 at 10:06:28 AM UTC+8, casuser wrote: > > Hello Mike, > > We are also having the same problem. Did you able to solve

[cas-user] CAS 5.3.x [SAML] + [Attribute Consent] seems not working + my workaround

Hi all, I have been testing [*SAML*] + [*Attribute Consent*] behavior, and I found that it works on CAS 5.2.x but *not working* on CAS 5.3.x by default. *CAS 5.2.x **Behavior:* 1. Initialized Login with SAML 2. Login 3. Show attribute consent page 4. Click confirm (With consent set to Attribute