J4 Issue ?
avatar schnuti
schnuti
1 Jun 2018

Steps to reproduce the issue

Was there a reason to remove this check from checkToken() in Session.php?

		if ($token === $app->input->server->get('HTTP_X_CSRF_TOKEN', '', 'alnum'))
		{
			return true;
		}

It's still handled and set in core.js - function Joomla.request

One of them is a bug.

avatar schnuti schnuti - open - 1 Jun 2018
avatar joomla-cms-bot joomla-cms-bot - change - 1 Jun 2018
Labels Added: ?
avatar joomla-cms-bot joomla-cms-bot - labeled - 1 Jun 2018
avatar franz-wohlkoenig franz-wohlkoenig - change - 1 Jun 2018
Category Authentication
avatar brianteeman brianteeman - change - 2 Jun 2018
Labels Added: J4 Issue
avatar brianteeman brianteeman - labeled - 2 Jun 2018
avatar franz-wohlkoenig
franz-wohlkoenig - comment - 12 Jun 2018

Can an more experienced User than me please answer as this Issue is set on "New" since 11 Days?


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/20642.

avatar franz-wohlkoenig franz-wohlkoenig - change - 12 Jun 2018
Status New Information Required
avatar mbabker
mbabker - comment - 12 Jun 2018

Probably lost in a merge conflict, not intentionally removed.

TBH, it's time to deprecate the static methods in the CMS Session class and we should look at how to transition to the application's checkToken method.

avatar franz-wohlkoenig
franz-wohlkoenig - comment - 12 Jun 2018

thanks for Comment, @mbabker

avatar franz-wohlkoenig franz-wohlkoenig - change - 12 Jun 2018
Status Information Required Discussion
avatar brianteeman
brianteeman - comment - 17 Jun 2018

closed see #20786

avatar brianteeman brianteeman - change - 17 Jun 2018
Status Discussion Closed
Closed_Date 0000-00-00 00:00:00 2018-06-17 21:50:07
Closed_By brianteeman
avatar brianteeman brianteeman - close - 17 Jun 2018

Add a Comment

Login with GitHub to post a comment