Getting an extranious "Sign in button" I can't find a way around

  • I’m using oauth2-proxy to redirect users into auth0, this works.
  • Auth0 if confi\gured with a Authentication/Social to authenticate to, this works.
  • I have 2 actions created one for to work and the other to validate roles in auth0, this works.

When oauth2-proxy redirects to I’m prompted with a “Sign in with CILogon” button. I want to skip this superfluous step and go straight to CILogon.

I noted this related thread but the solution there hasn’t made any change to me: Button before login auth0

The 302 redirect to auth0 is this URL, it’s to /authorize as described in the thread above.

The sequence of redirects from my webserver to auth0 is as follows:<obfuscated>&<obfuscated>

After my web server 302-redirects to auth0, auth0 produces a 302 redirect to:<obfuscated>&protocol=oauth2&approval_prompt=auto&

I tried playing with approval_prompt, it was set to “forced” by default, I tried “auto” (per a debug thread) as well as other obvious things like “false”.

I’m not sure what’s causing the login button on auth0 to display prior to the redirect to “social” cilogon org.


Hey @braingeneers-admins

According to, you should be able to bypass the login screen if you pass a connection param with the name of the custom social connection directly to the /authorize request.

More details can be found here as well

Let me know if that solves your issue!

1 Like

That was it, thanks. In fact I already had the connection parameter (technically chatgpt had already included it) but it gets dropped by oauth2-proxy (an issue now open at their github - oidc auth redirect drops the `connection` parameter as defined in `login_url` unexpectedly · Issue #2702 · oauth2-proxy/oauth2-proxy · GitHub). It works when I manually inject that parameter to the redirect URL, so all is well on the auth0 side. Thanks for the helpful reply.