How to trigger "2 Different IP Countries in 1 hour"?

Hi Josh,

Could you please provide the request payload for your ../users/register API call.  While you did indicated that you used LoginInput objectType to login, I need to determine which objectType you have used when you registered, in order to help you with the your inquiry. Please make sure to remove any sensitive data before submission.

Thank you!

Hakim

No sensitive data here, all test data.

These are the register, login, and validate payloads I used for the original path.

To simulate the phishing attempt, I changed clientIP to "95.173.136.71" in login and validate, and I changed sessionID to "00000002" in validate.

In order to see the desired result, you will need to register using "objectType": "AdaptiveRegisterUserInput" attribute in your JSON payload, and then login using "objectType": "AdaptiveLoginInput".  

When you call "/users/{userID@domain}/login" endpoint the second time simulating an IP from another country, like in step 6, you must receive a "riskResponseCode" attribute with a value that represent the authentication challenge associated with this type of behaviour, for example it could be '2' for "Challenge", or '23' for "ChallengeFingerprint", depending on your Risk Analytics instance setup to step up the authentication.  The value for your first login should be '0' for "Accept", if you used the default request body.

Coming to the important part of your question, when you have called "/users/{userID@domain}/events/validate" to validate your login, you should have called the endpoint using "eventType": "LoginAttempt" rather than "eventType": "LoginSuccess", if you take a look into your latest events in Risk Analytics for your login attempts, you will see their event type fields are filled as "LoginAttempt" and not "LoginSuccess", so in step 7, you should have validated using "LoginAttempt" in your request.  Then you will have a response body with the same "riskResponseCode" you had following your login attempt, and a "sessionStatus" as "unknown" until you have completed the required authentication. 

Please note that if you chose to set up your response code to a value that requires a device to authenticate, like "ChallengeFingerprint", you will need first to activate that device to be your trusted device, otherwise you will receive '409' error code.

Please let me know how it works for you.

Thank you for your response. When I change the eventType to LoginAttempt, the Russian IP address gets the riskResponseCode of 2 and a sessionStatus of unknown, and I can see that the rule was fired in the Risk Analytics dashboard. So that answers my original question, and now I see that the parent rule's campaign criteria is set up to trigger on LoginAttempt, so I understand why it needed to change.

I do get the 409 response from the generate-secure-challenge API, but that's expected behavior. I haven't yet installed your Android app on my phone and performed the activation. That's next on my list.

The AdaptiveRegisterUserInput works fine for me. However, when I try to log in with the AdaptiveLoginInput, I get a 500 error code response, and I didn't see any indication of what I might have done wrong. I attached the JSON payloads for both calls.

I am glad you reached there.

As for the latest error code you had with AdaptiveLoginInput, what seems to cause the issue is in "02-users-login-adaptive-POST_request.txt" file, "sessionID" should have been written with an uppercase D in ID.

Yes, that was it. Thanks again.

You are welcome.  Glad that helped.