You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See dialog that asks for additional login (here example in Polish):
See mobile session present in web UI.
Expected behaviour
After successful authentication with client certificate, device should be authorized to use nc without any other confirmations, permissions, tokens, passwords.
Actual behaviour
Login dialog is shown as above.
Android version
up to date
Device brand and model
Stock or custom OS?
Stock
Nextcloud android app version
4.6
Nextcloud server version
28.0.4
Using a reverse proxy?
Yes
Android logs
No response
Server error logs
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
I'm not sure how I can read a user id from a client certificate. In my setup (see #12931) I would be happy to just get a client certificate checked correctly on the reverse proxy regardless of the user of the certificate.
Having the client certificate just to set a higher security level on the TLS connection would be enough.
I'm not sure how I can read a user id from a client certificate.
TLS may be terminated on reverse proxy or web server and user_saml may provide user id to nc from environment variable (set by Apache for example). No need to pass user id from client to server separately. If client must know user id for something, should query nc API for it.
Steps to reproduce
Expected behaviour
After successful authentication with client certificate, device should be authorized to use nc without any other confirmations, permissions, tokens, passwords.
Actual behaviour
Login dialog is shown as above.
Android version
up to date
Device brand and model
Stock or custom OS?
Stock
Nextcloud android app version
4.6
Nextcloud server version
28.0.4
Using a reverse proxy?
Yes
Android logs
No response
Server error logs
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: