I only able to provide the last group...
I use the cas.authn.attributeRepository.ldap[0]....
I also set the cas.authn.attributeRepository.ldap[0].allowMultipleDns=true
cas.authn.attributeRepository.ldap[0].allowMultipleEntries=true
cas.authn.attributeRepository.ldap[0].allowMultipleEntries=true
Any Idea how to set a multi value?
i query all the groups with ldap://ldap_host '(&(objectClass=posixGroup)(memberUid={user}))'
and I know some user belongs to several groups but it only reports the last one
Hello, I have set up CAS with WSFED and the default configuration given by the documentation (https://apereo.github.io/cas/6.2.x/configuration/Configuration-Properties.html#ws-fed-delegated-authentication) but when I head over to the log-in page it says "Authorization Denied" and i get redirected to "/cas/wsfedredirect?wsfedclientid=77f30f54-6150-46a7-a75d-7518af062c55". So... I know something is working atleast. I suspect that I need more than "org.apereo.cas:cas-server-support-wsfederation-webflow:${project.'cas.version'}" as dependency to make this work. Any guidance?
Hi, I have a CAS setup for 2-factor authentication and it works fine with Chrome browser but with I.E the 2FA window doesn't show up. This appears to be the problem with URL length limit in I.E https://support.microsoft.com/en-us/help/208427/maximum-url-length-is-2-083-characters-in-internet-explorer
Any suggestions on the above query is highly appreciated
Hi Francisco, you have to permit attribute release, see https://apereo.github.io/cas/6.2.x/integration/Attribute-Release-Policies.html.
I received the above warning and the integration failed
2/3 people just miss to scan this code and click next
You can delete the QR records of these users in the records and let the users re-register
cas 5.3.2 客户端通过SecurityUtils.getSubject().getPrincipals() 获取的Map为空，但是id又能获取到 这是为什么呢？
my organization has a long history with CAS, and about 9 years ago we wrapped our web services in CAS w/ CAS Protocol 2.0... and i'm trying to figure out a better way to handle webapp and thick client authentication to web services with something like a JWT bearer token that can be sent on every request, and doesn't require handling an expired cookie/session and catching 302 redirects... i.e. what is a good transparent method for simple CAS secured API authentication?
Hello everyone, there seems to be a weird behaviour with the CAS audit log on CAS 6.2.X using SAML with Google Auth MFA. When a user provides a wrong OTP value and authentication fails the audit log file shows the following entry, which seems to have the WHO incorrectly logging the token value instead of the username. Any ideas ? :
Audit trail record BEGIN =============================================================
WHO: 039328
WHAT: Supplied credentials: [OneTimeTokenCredential(token=039328)]
@bloodmc the No cookie, I believe is from a user who is leveraging browser history of a poorly created bookmark. Not 100% sure.
Hi All. I'd like to ask what is the "normal" performance of a login action in CAS. In our fresh environment is aboutn 5 seconds, and we see every time a user logs-in, the processor goes up to 100% for about 3 or 4 seconds. Is this a normal behavior? We are using a VM in Azure with 2 processors and 4GB RAM (just 1GB in use as it is not in production yet).