If we first sign into Service A successfully using Username, Password, and MFA Token and then attempt to navigate to the URL for Service B this works well (as expected).
However, if we attempt to specify bypass rules for bypassing MFA based on a principal attribute (either using cas.properties or groovy script), when we access Service B after successfully authenticating with Service A, CAS forces a re-authentication of the user for Service B. This seems to work fine as long as we do not enable MFA bypass (plain MFA works).
We have asked in the CAS Community and have not heard back from anyone having the same issue. Does bypass require special configuration? We dont want to report an issue if this is due to a misconfiguration/mistake at our end. We'd be happy to help with researching a solution for this but are not clear about where to start looking and what the flows are. Any help would be appreciated.