Authentication Scheme Protection Level Ignored When Changing The TARGET Parameter of Login FCC

Document ID : KB000117253
Last Modified Date : 10/10/2018
Show Technical Document Details
Using a lower authentication scheme protection level set of credentials, we are able to obtain a higher session level only by tampering the target. 

This means that we took the form login with protection level 10 and changed TARGET with that from a level 15 resource, and we are able to access the resource(with level 10 credentials (username/password) 


1) Protected the first application (/web3) with forms Auth scheme 1(protection level 10) 

2) Protected the second application(/web4) with forms Auth scheme 2(protection level 15) 

3) Login to first application with forms Auth scheme 1(protection level 10), andd you get redirected to login page with target:

4) Once redirected to the form login, change the TARGET parameter in order to land to second application, protected with Auth scheme 2(protection level 15), and then call the link with the modified TARGET

5) Enter and submit the credentials and you should be able to access(/web4) using login Auth scheme 1(protection level 10) 

How can we resolve this?
Policy Server 12.52 SP1 CR6 on RedHat 6 64bits 
Webagent 12.52 SP1 CR6 with Apache/2.2.15 64bits on RedHat 6 64bits 
The issue has been identified in FCCCompatMode 
Set FCCCompatMode to No