This message was deleted.

yes i got it working and got a blog on it https://c4rm0.wordpress.com/add-a-eula-into-netscaler-nfactor-flow/

Awe, yes, thank you, I have it book marked and forgot about this. I can modify the structure to my needs.

your issue sounds like you need to add password credential index to your login schema and then use a traffic policy that looks for the SSO password expression AAA.USER.ATTRIBUTE(1)

I really like what nFactor can do, and yet, it was completely unnecessary to make the implementation of it so complicated.

what ever is last in your Nfactor chain will be passed to storefront - When performing Single Sign-on to StoreFront, nFactor defaults to using the last entered password. If LDAP is not the last entered password, then you need to create a Traffic Policy/Profile to override the default nFactor behavior.

Damnit, I was afraid of that. That is why I asked the question in here. I was floating on that river in Egypt trying to avoid re-arranging the factors.

if you add the password credential index to your loginschema and use the traffic policy that looks for the sso password expression you should be able to get round that

I’ll give that a shot.