[Solved] Auth token may be an issue

Hi, Antonio and crew. Me again. (sigh)
I upgraded to Moodle 2.8.1 a while back -- all went fantastic. Still very happy with Joomdle.
About a week ago, I upgraded Joomla from 2.5.28 to 3.3.6 and upgraded Joomdle from .95 to 1.0. (Congratulations, btw...)

The system health check shows all green except the last item which shows a red x and invalid token error. I've confirmed that is the same token that is in Joomla and in Moodle. I re-generated the token after adding the new services.
The bridge seems to be working -- mostly. I read in the documentation that I can safely ignore the error...but just noticed that my user profiles in Moodle weren't being filled out. Students were being redirected to fill in their profile, but they couldn't fill it in.
I looked at the auth plugin and realized that the mandatory fields were locked, so that was probably the issue. I've unlocked them.
My question is: do you think I'll be okay now? Do you think I *can* safely ignore that error?
Or do you have a thought as to why this is showing up now?
It has been all green on the back-end for a long time...just this latest Joomdle update shows that one red x.
I'm nervous. Wondering what I've missed THIS time...lol :dry:
Just wondering if in your wisdom you can point me in the right direction...

If the last item is showing a red X, you will want to fix that. The only two that can be ignored sometimes are the two above that. The symptoms you are receiving re user profile are probably like caused by the red x problem.

The lock fields, can be lock if
1) you have a method of collecting the data in joomla such as joomla profile, shop profile, social profile, etc.
2) joomla is connecting to moodle correctly and passing the data

The fact that you previously working with lock fields without error but now you are not suggests an issue during the upgrade. The message you get with the red x is token related. With version 1.0 of Joomdle IP addresses are no longer required. Instead tokens are used in both directions. Did you generate a Joomla token and enter it in Moodle? Note: This is new. Previously you created a token in Moodle and entered it in Joomla - now it is both ways.

Did you entered in Joomdle in Moodle the new auth token generated in Joomdle config in Joomla?
That messages appears when token is not valid.

Thank you both for that!!!
I knew you'd know exactly what I'd messed up. I was putting the same auth token in both places.
NOW I get it.
THANKS!