Hi
Thanks for your answer, unforunately it does not work for me. I'm setting the first variable within an iRule, and the second one trough a Logon Page. I tried different scenarios with the folowing Results:
iRule:
ACCESS::session data set session.user.otp.pw "1234"
LogonPage:
Type:"text" Post Variable Name:"otp" Session Variable Name:"otp"
Compare:
expr { [mcget {session.user.otp.pw}] equals [mcget {session.logon.last.otp}] }
Result: This Scenario does work
iRule:
ACCESS::session data set session.user.otp.pw "1234"
LogonPage:
Type:"password" Post Variable Name:"otp" Session Variable Name:"otp"
Compare:
expr { [mcget {session.user.otp.pw}] equals [mcget -secure {session.logon.last.otp}] }
Result: This Scenario does not work
iRule:
ACCESS::session data set -secure session.user.otp.pw "1234"
LogonPage:
Type:"text" Post Variable Name:"otp" Session Variable Name:"otp"
Compare:
expr { [mcget -secure {session.user.otp.pw}] equals [mcget {session.logon.last.otp}] }
Result: This Scenario does not work
iRule:
ACCESS::session data set -secure session.user.otp.pw "1234"
LogonPage:
Type:"password" Post Variable Name:"otp" Session Variable Name:"otp"
Compare:
expr { [mcget -secure {session.user.otp.pw}] equals [mcget -secure {session.logon.last.otp}] }
Result: This Scenario does not work
So the only Scenario that works is the one without the "-secure" option. Is there a global Setting witch prevents me to access secure Variables even with the "-secure"-Option? I have no idea why it works for you but not for me.
Best Regards
sbu