OCIS Login fails with Status 500

Infinite Scale
1

Steps to reproduce

  1. Attempt login with admin user / password

Expected behaviour

Successful login

Actual behaviour

GUI displays: Unexpected HTTP response: 500. Please check your connection and try again.

Server configuration

Operating system:
K8s / Debian

Web server:

Database:

PHP version:

ownCloud version: (see ownCloud admin page)
2.0.0

Updated from an older ownCloud or fresh install:
Fresh install

Where did you install ownCloud from:
Helm Chart v0.1.0: owncloud/ocis

The content of config/config.php:
None

List of activated apps:

files
user-management

Are you using external storage, if yes which one: local/smb/sftp/…
S3

Are you using encryption: yes/no
no

Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/…
no

Client configuration

Browser:
Chrome

Operating system:
Windows / Android

Logs

IDP pod log

{"level":"error","service":"idp","error":"ldap identifier backend logon connect error: LDAP Result Code 49 \"Invalid Credentials\": ","time":"2023-05-02T08:29:36.306449058Z","message":"identifier failed to logon with backend"}

{"level":"debug","service":"idp","request-id":"668e72181489ca7a83cf4b75efc85848","proto":"HTTP/1.1","method":"POST","status":500,"path":"/signin/v1/identifier/_/logon","duration":35.827354,"bytes":44,"time":"2023-05-02T08:29:36.306550884Z"}

IDM pod log

{"level":"debug","service":"idm","time":"2023-05-02T08:29:36.306157562Z","message":"DN: 'uid=idp,ou=sysusers,o=libregraph-idm' not found"}

{"level":"error","service":"idm","bind_dn":"uid=idp,ou=sysusers,o=libregraph-idm","op":"bind","remote_addr":"10.244.5.107:60526","time":"2023-05-02T08:29:36.306204849Z","message":"not found"}

{"level":"debug","service":"idm","bind_dn":"uid=idp,ou=sysusers,o=libregraph-idm","op":"bind","remote_addr":"10.244.5.107:60526","time":"2023-05-02T08:29:36.306235333Z","message":"Entry 'uid=idp,ou=sysusers,o=libregraph-idm' does not exist"}

Any help to debug this problem would be greatly appreciated…

Best regards,
Eric.

2

Is this still an issue or where you able to resolve this?

3

Hello; This is still a problem. I have used the documentation: Container Setup

{"level":"error","service":"idm","bind_dn":"uid=idp,ou=sysusers,o=libregraph-idm","op":"bind","remote_addr":"127.0.0.1:48288","time":"2023-11-04T19:19:38.100219579Z","message":"invalid credentials"}
{"level":"error","service":"idp","error":"ldap identifier backend logon connect error: LDAP Result Code 49 \"Invalid Credentials\": ","time":"2023-11-04T19:19:38.100429527Z","message":"identifier failed to logon with backend"}
4

This looks like a different issue, it says invalid credentials. You might have leftover data in your ocis-config and/or ocis-data volume. Those might cause this.

5

Thanks for the quick feedback; I cleaned up the folders of the volumes, but the result was always the same under 4.0.2 and 5.0.0.

Now I am one step further, it’s because of the variable, if the real hostname is set the login doesn’t work.
OCIS_URL=https://<your-hostname>:9200
In the Quick Guide it’s a bit different and this works: Quick Guide
OCIS_URL=https://localhost:9200

Any idea how to add other functions besides Files Services?

6

I am not sure what the issue here is, what do you mean by “set the real hostname” is it set to a FQDN?

What do you mean by other functions besides Files Services? If you mean apps like oc classic, that does not exist yet. But feel free to contribute any :slight_smile:

7

Yes

Ok, thanks for the info.

8

Is the FQDN resolvable from within the running image?