400: redirect_uri_mismatch

[Matti Jordman]

Hi

I'd upgrade my Tsugi test server after almost 1.5 years. Tools works fine but I can't login as admin.

I'm getting 400: redirect_uri_mismatch

Oauth2 Client Id and secret are correct... 

Any ideas?

br matti

[charles....@apereo.org]

Matti,

This is not much to go on.  The redirect_uri_mismatch is something happening as part of an LTI 1.3 launch, right?   Logging in as admin seems orthogonal.

I need a bit more details - feel free to contact me directly - happy to get on a Zoom.

/Chuck

--
You received this message because you are subscribed to the Google Groups "Tsugi Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tsugi-dev+...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/tsugi-dev/7c1abb9f-4db6-462b-ab17-01bfe76aee63n%40apereo.org.

[Matti Jordman]

Hi Chuck

The problem is with website login. I'll try to solve this and let you know if I don't find any solution...

Thanks!

br matti

To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/tsugi-dev/56a7e33a-f348-441c-9dc5-093308b91f09%40apereo.org.

[David P. Bauer]

Hi Matti,

Is this an issue with Google authentication? It may be that you need to set this to false in your config.

// This is a legacy backwards compatibility.   In the round-trip to Google it used to
// come back login.php after login was successful - If this is true, we come back
// to login (without the php) - set this to false to restore the old pattern
$CFG->google_login_new = false;

David

To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/tsugi-dev/7a306817-3294-4408-9428-d62c130c9145%40gmail.com.

--

David P. Bauer
Director, Online Learning Technology & Strategic Initiatives
Center for Online Learning
Roesch Library, LTC 034
Office: (937) 229-2074
Support: (937) 229-5039

[Matti Jordman]

Hi David

Yes, that's it.

I probably have to check the whole config.php file if there's something else new...

Thanks!

br matti

[Chuck Severance]

Matti,

If you have been away form master for a while there are a few little things that might happen in config.php.

The good news is that they chow up quick and are easy to fix.   The biggest problem is that PHP 8.x does not like adding properties to a class after it has been created.   For example in my config.php I have lines like:

$CFG->chucksfunthing = “true”;

This throws a warning.  The Post-PHP-8.3 pattern (make sure you are up to lastest master is:

$CFG->setExtension(‘chucksfunthing’, ’true’); 

and then later

if ( $CFG->getExtension('chucksfunthing’, ’false’) != ’true’ ) …..

But again for me those showed up really quick and on every page that includes config.php (most pages).

It is a good idea to run through your site watching the error log - sometimes errors don’t make it to the screen.

Most should be easy and quick fixes.

Being on a modern PHP is worth it.

/Chuck

To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/tsugi-dev/d26db29f-c05f-48c2-9f2c-f5bc435e33b6%40gmail.com.

[Matti Jordman]

Hi Chuck

Thanks for all help!

br matti

[Charles Severance]

Matti,

If there were any other bumps on the road to PHP 8.2, let us know. If there were no bumps - then I am pretty happy with how we managed the transition.

Thanks and Happy New Year.

/Chuck