GitNext doesn't work with forgejo behind reverse proxy with mTLS #1399

# Describe your matter briefly

I reach my forgejo instance via a reverse proxy with compulsory mutualTLS authentication.
I use this setup on windows, firefox on linux, chrome on android.
I wanted to try GitNext: After I press login no propt about certificate appears and an error instead (We cannot reach the server ...)

What did you expect?

Expecting the prompt that ask me which certificate to use and login

Some additional details

• The version of Gitea you are using: Forgejo-8.0.1+gitea-1.22.0
• The version of GitNex you are using: 6.0.0
• Source of installation (Play Store, F-Droid, APK): APK
• Current android version and phone model/manufacturer: MIUI14 / Android12
• The type of certificate your instance is using (self-signed, signed): signed (reverse proxy)
• How you used to log in (via password or token): password
  
  

We would appreciate some screenshots or stacktrace's, but this is also not required.

how?

• I carefully read the contribution guidelines.
  
  

GitNex does not support mTLS.

Have you tried the token option?

GitNex does not support mTLS.

Have you tried the token option?

I actually never used them yet. Any help for the token permissions? They seem pretty hazardous things.

I tried the token based auth and I got the same error message.

At this point I am pretty confident that you meant token based login without the mTLS layer and I cannot remove such layer.

I hoped GitNex used the Android Cert Store or Keystore, I dont know how it is called, maybe "user certificate storage".

Thank you

GitNex does support Android key store, you can try to add your certificates via: https://github.com/labnex/LabNex/wiki/FAQ#does-labnex-support-self-signed-certificates

The wiki is for LabNex, but it is the same process. If its working and you confirm it, I will add it to GitNex wiki.

Part to follow:

• Install the certificate on your Android device using Google's official guide

Install GitNex 11.0.0 for testing.

@mmarif I believe the issue which @kuolemaa has (which I also have) is that we cannot authenticate to Gitea instances behind mTLS authentication (Client Certificates) using GitNex.

This is not addressed by https://github.com/labnex/LabNex/wiki/FAQ#does-labnex-support-self-signed-certificates.

It would be awesome if it were possible to get mTLS proxy authorization support, just like we now have basic auth proxy authorization.