apereocas-bot on gh-pages
Published docs to [gh-pages] fr… (compare)
mmoayyed on master
fix tests; update rel notes (compare)
mmoayyed on 6.3.x
fix/force radius version for jr… (compare)
apereocas-bot on gh-pages
Published docs [gh-pages]. (compare)
apereocas-bot on gh-pages
Published docs to [gh-pages] fr… (compare)
mmoayyed on master
additional tests fix build additional puppeteer tests to h… and 28 more (compare)
mmoayyed on 6.3.x
fix styling issues (compare)
mmoayyed on 6.3.x
backport patch for saml2 async fix build with jcifs dependency Add possibility to flexible mat… and 1 more (compare)
apereocas-bot on gh-pages
Published docs to [gh-pages] fr… (compare)
apereocas-bot on gh-pages
Published docs [gh-pages]. (compare)
mmoayyed on master
Add possibility to flexible mat… (compare)
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)]