impress/app/controllers/devise/omniauth_callbacks_controller.rb

class Devise::OmniauthCallbacksController < ApplicationController
	def neopass
		render plain: request.env["omniauth.auth"].uid
	end

	def failure
		render plain: "Failure"
	end
end
Add hidden "Log in with NeoPass" button, to placeholder login strategy If you pass `?neopass=1` (or a secret value in production), you can see the "Log in with NeoPass" button, which currently takes you to OmniAuth's "developer" login page, where you can specify a name and email and be redirected back. (All placeholder UI!) We're gonna strip the whole developer strategy out pretty fast and replace it with one that uses our NeoPass test server. This is just me checking my understanding of the wiring! 2024-03-14 15:34:24 -07:00			`class Devise::OmniauthCallbacksController < ApplicationController`
NeoPass strategy interacts with dev NeoPass server, which is still WIP In this change, we wire up a new NeoPass OAuth2 strategy for OmniAuth, and hook up the "Log in with NeoPass" button to use it! The authentication currently fails with `invalid_credentials`, and shows the `owo` response we hardcoded into the NeoPass server's token response. We need to finally follow up on the little `TODO` written in there! 2024-03-14 16:13:31 -07:00			`def neopass`
Read and customize the username reported by `neopass-server` Okay, `sub` seems to be a pretty standard place for user identifiers. Let's start with that assumption! I override the `oauth2-mock-server`'s default of `johndoe` with `theneopetsteam`, just to be cute :3 2024-03-14 18:19:45 -07:00			`render plain: request.env["omniauth.auth"].uid`
Add hidden "Log in with NeoPass" button, to placeholder login strategy If you pass `?neopass=1` (or a secret value in production), you can see the "Log in with NeoPass" button, which currently takes you to OmniAuth's "developer" login page, where you can specify a name and email and be redirected back. (All placeholder UI!) We're gonna strip the whole developer strategy out pretty fast and replace it with one that uses our NeoPass test server. This is just me checking my understanding of the wiring! 2024-03-14 15:34:24 -07:00			`end`
NeoPass strategy interacts with dev NeoPass server, which is still WIP In this change, we wire up a new NeoPass OAuth2 strategy for OmniAuth, and hook up the "Log in with NeoPass" button to use it! The authentication currently fails with `invalid_credentials`, and shows the `owo` response we hardcoded into the NeoPass server's token response. We need to finally follow up on the little `TODO` written in there! 2024-03-14 16:13:31 -07:00
			`def failure`
			`render plain: "Failure"`
			`end`
Add hidden "Log in with NeoPass" button, to placeholder login strategy If you pass `?neopass=1` (or a secret value in production), you can see the "Log in with NeoPass" button, which currently takes you to OmniAuth's "developer" login page, where you can specify a name and email and be redirected back. (All placeholder UI!) We're gonna strip the whole developer strategy out pretty fast and replace it with one that uses our NeoPass test server. This is just me checking my understanding of the wiring! 2024-03-14 15:34:24 -07:00			`end`