I suspect it may due to the log in process coming from a different origin, however, the configuration update to enable CORS should take care of that