CSRF Token Mismatch after ajax call in login form

Can you describe more precisely what you are trying to achieve please ?

So, I have a login form with an email and password field. When the user blurs off of the email field it executes an ajax call to a findUserType method in my controller. That method determines if the user is a DB authenticated user or a SAML/OAuth authenticated user. If SAML/OAuth it will return the redirection info and the ajax return method will redirect. If the user is a DB user, it will activate the password field to accept user input. However, when I enter the password and submit the form I get a Token Mismatch error. I'm guessing, cause I don't really know how to verify it, that the CSRF token is updating on the backend when this ajax call is made, and the cookie on the browser end then has the wrong token. I am returning the the crsf token, but it doesn't appear to be encrypted and I'm not sure how to update the browser side cookie value so that when the user hits "login" is submits the correct csrf token and avoids the mismatch.

So, to be clear, the ajax call happens after the form is loaded but before the form is submitted. So I guess I just need to know how to properly update the csrf token in the form so when it is submitted it matches.

facepalm

I was doing this to myself with a header modifier plug I use for testing....

@jgreen You need to send a csrf token with your ajax request OR you may do a GET OR you may disable csrf verification.
You may follow the following links
1.ajax-in-laravel-5
2.csrf-form-submit-through-ajax-call
3.laravel-csrf-filter-with-ajax-support

yes, I was sending it, I was just under the impression that it would be changing from request to request, which is not the case. Turns out I was overwriting that header with a plug I use for testing and that resulted in null values from the request object. So it was totally my bad....