Redirection to Privatebin after Oauth2-proxy not working

[GopalGupta1805]

Describe the problem/question

I have Privatebin setup in K8s cluster which has Oauth in-front of this. When opening a secret URL like https://example.com/?<key>#<value> after successful authentication, It lands on an empty page shared below instead of the same URL that was hit previously

Did you use the FAQ section?

• Yes, I have read the FAQ and I found no solution/answer there.

What you did?

1. Setup Privatebin chart in GKE K8s cluster
2. Setup Oauth2-proxy chart in GKE K8s cluster in front of above chart
3. Setup nginx-ingress for loadbalancer in front for both
   ...

What happens

When opening a secret URL like https://example.com/?<key>#<value> after successful authentication, It lands on an empty page

What should happen

Instead it should land on page which has secrets that is shared on it.

Additional information

No response

Server address

No response

Server OS

No response

Webserver

No response

PrivateBin version

No response

Browser and version

No response

Local operating system and version

No response

Issue reproducibility

Yes, reproducible on https://privatebin.net.

[elrido]

You will have to review the exact requests and redirects issued by your setup, for example using your browsers F12 console using the network traffic tab. Very likely, the oauth server tries to redirect you back to the original page, but it won't have access to the hash-part of your URL (the bit after the "#" which is the secret key of the paste) and so the privatebin application will switch into the "new paste" mode.