cloudreve / cloudreve/ios-feedback

Feature Request: Support mTLS client certificates or custom HTTP headers in iOS app

Open
#119 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
6
Forks
3
PR merge metrics
No merged PRs in 30d

Description

## Description

It would be useful if the Cloudreve iOS app could support mutual TLS (mTLS) client certificates and/or custom HTTP request headers when connecting to a Cloudreve instance.

This is particularly useful for users who expose Cloudreve through services such as Cloudflare Tunnel / Cloudflare Zero Trust, where an additional authentication layer can be enforced before requests reach the Cloudreve server.

## Use case

For example, a Cloudreve instance may be protected by Cloudflare using mTLS:

```
Cloudreve iOS App
|
| HTTPS + Client Certificate
v
Cloudflare
|
| Cloudflare Tunnel
v
Cloudreve
```

The web browser can use a client certificate configured in the operating system/browser, but the iOS app currently does not appear to provide a way to configure or select a client certificate.

Another common setup is to require a custom HTTP header at the reverse proxy, for example:

```
X-Cloudreve-Client:
```

The reverse proxy can then reject requests that do not contain the expected header.

Thanks!

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are named in the issue. Start by locating the iOS app's connection configuration and HTTP request setup, then determine how users would configure or select certificates and headers. Done means the app supports the requested authentication options when connecting through the described proxy setups.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios
Domain
authentication, mobile, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.