Obsidian Login block causes an "Error 400: invalid_request" when using Google Authentication

[leahjennings]

Please go through all the tasks below

• Check this box only after you have successfully completed both the above tasks

Please provide a brief description of the problem. Please do not forget to attach the relevant screenshots from your side.

When Google Authentication is used with the new Obsidian Login block after clicking Sign in with Google, Google's authentication service gives the following error message: "You can't sign in to this app because it doesn't comply with Google's OAuth 2.0 policy for keeping apps secure."

My theory is that the redirect_uri getting passed to Google is missing a / character from the path:

And I think that's caused by line 741 in the Login.cs file

We use Google authentication with the Login (Legacy) block without any problems.

Expected Behavior

I would expect that once configured, the Google authentication process would complete and successfully return back to Rock as an authenticated person.

Actual Behavior

The Google services gives a "Error 400: invalid_request" and the login process is never completed.

Steps to Reproduce

• On a Rock server running v15.0 (this is the version I believe the Obsidian Login block was introduced), and with Google Authentication configured as an external auth type, navigate to the /Login page
• Remove the Login (Legacy) block
• Add the Obsidian > Security Login block

• Configure the block settings to allow Google authentication as a secondary authentication type

• Navigate to the login page and click on "Sign in with Google"
• Notice the redirect to the Google error message

Rock Version

Rock McKinley 15.0 (1.15.0.16)

Client Culture Setting

en-US