Docker opendcim/opendcim 23.01

[coreyman2000]

Getting this error when trying to log in with default dcim user.

The ldap_debug_password is set and only the user dcim is valid for recovery. Run UPDATE fac_Config SET Value='' WHERE Parameter='LDAP_Debug_Password'; to clear the debug password.

here is my docker compose

version: '3'
services:
opendcim:
image: opendcim/opendcim:21.01
ports:
- 80:80
depends_on:
- db
environment:
- OPENDCIM_DB_HOST=db
- OPENDCIM_DB_NAME=opendcim
- OPENDCIM_DB_USER=root
- OPENDCIM_DB_PASS=your_mysql_password
- OPENDCIM_AUTH=LDAP

db:
image: mysql:5.7
volumes:
- ./db_data:/var/lib/mysql
environment:
- MYSQL_ROOT_PASSWORD=your_mysql_password
- MYSQL_DATABASE=opendcim

[LFrank2021]

Pulling 21.01 is intentional?
Is moist likely not the solution to your problem, but it is a discrepancy.
Did you try dcim/dcim?
I think I heard as much in the according YouTube video.

[coreyman2000]

looks like i was trying different versions i tired both, on 23.01 now and yes no matter the account dcim:dcimpassword
or dcim/dcim both show the same error, i deleted the DB and source files again and still no luck :(

The ldap_debug_password is set and only the user dcim is valid for recovery. Run UPDATE fac_Config SET Value='' WHERE Parameter='LDAP_Debug_Password'; to clear the debug password.

i also tried on a different docker host and same error :(

[coreyman2000]

ran wireshark and noticed
Expires: Thu, 19 Nov 1981 08:52:00 GMT, why would this date bad is there something wrong with apace or my local chrome?
username=dcim&password=dcimpassword&submit=SubmitHTTP/1.1 200 OK
Date: Tue, 11 Jul 2023 15:19:17 GMT
Server: Apache/2.4.52 (Ubuntu)
Set-Cookie: PHPSESSID=pe17llnc7brllm57337jiv3paf; path=/; secure; HttpOnly
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 4270
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html; charset=UTF-8

[coreyman2000]

turns our password is dcimadmin however still just returns to login screeen :(

[samilliken]

I am struggling to understand what you are actually trying to ask here. Is this a new db or a migration from an existing one?

[bhoglo]

@samilliken I am actually having the same issue described by @coreyman2000. It's a fresh install of mariaDB 11 and openDCIM 23.01 containers. It proceeds through the install.php->container-install.php process initially, and then brings you to a login screen. I've verified the database is actually being populated. If you attempt to use anything other than the dcim account with the LDAP_Debug_Password, you get the error mentioned above (expected). If you use the dcim/dcimadmin login, it just spits you back out at the login screen with no errors (not expected). I am not able to login and view the actual site. I've tried clearing the debug password, but that didn't change any outcome (as expected). Below is the screenshot of all I can access.

[samilliken]

What environment variables are you passing to the container? Scott From: Blake Sent: Friday, July 21, 2023 9:37 AM To: opendcim/openDCIM ***@***.***> Cc: Scott Milliken ***@***.***>; Mention ***@***.***> Subject: Re: [opendcim/openDCIM] Docker opendcim/opendcim 23.01 (Discussion #1395) @samilliken <https://github.com/samilliken> I am actually having the same issue described by @coreyman2000 <https://github.com/coreyman2000> . It's a fresh install of mariaDB 11 and openDCIM 23.01 containers. It proceeds through the install.php->container-install.php process initially, and then brings you to a login screen. I've verified the database is actually being populated. If you attempt to use anything other than the dcim account with the LDAP_Debug_Password, you get the error mentioned above (expected). If you use the dcim/dcimadmin login, it just spits you back out at the login screen with no errors (not expected). I am not able to login and view the actual site. I've tried clearing the debug password, but that didn't change any outcome (as expected). Below is the screenshot of all I can access. <https://user-images.githubusercontent.com/5169910/255187350-60c2d9f8-8b26-4445-b5dc-62bb24534565.png> — Reply to this email directly, view it on GitHub <#1395 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMTY64FJU5M3UXE2WG2WSTXRKAYFANCNFSM6AAAAAA2S3M7SA> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AAMTY63XI2KH4YCMM257RUTXRKAYFA5CNFSM6AAAAAA2S3M7SCWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAMNKQQ.gif> Message ID: ***@***.*** ***@***.***> >

[bhoglo]

environment:
  - OPENDCIM_DB_HOST=localhost
  - OPENDCIM_DB_PORT=3306
  - OPENDCIM_DB_NAME=dcim
  - OPENDCIM_DB_USER=dcim
  - OPENDCIM_DB_PASS=Xit4PoduKid5Mifp
  - OPENDCIM_AUTH=LDAP
  - TZ=America/Chicago

[samilliken]

So after you login with the ldap debug password, you can’t get to the Configuration screen to put in your actual LDAP configuration? Scott From: Blake Sent: Friday, July 21, 2023 9:54 AM To: opendcim/openDCIM ***@***.***> Cc: Scott Milliken ***@***.***>; Mention ***@***.***> Subject: Re: [opendcim/openDCIM] Docker opendcim/opendcim 23.01 (Discussion #1395) environment: - OPENDCIM_DB_HOST=localhost - OPENDCIM_DB_PORT=3306 - OPENDCIM_DB_NAME=dcim - OPENDCIM_DB_USER=dcim - OPENDCIM_DB_PASS=Xit4PoduKid5Mifp - OPENDCIM_AUTH=LDAP - TZ=America/Chicago — Reply to this email directly, view it on GitHub <#1395 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMTY67WBTSAFEWPCBSGV2LXRKCXZANCNFSM6AAAAAA2S3M7SA> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AAMTY63JBOACXMYKU6AKAI3XRKCXZA5CNFSM6AAAAAA2S3M7SCWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAMNK2E.gif> Message ID: ***@***.*** ***@***.***> >

[bhoglo]

That is correct. It will not bring me to the configuration screen. It will POST to login_ldap.php -> redirect to index.php -> then redirect to login_ldap.php.

[samilliken]

I just tested with a fresh, empty db on 23.01. Logged in as dcim/dcimadmin Was able to click on Edit Configuration Then I could setup an actual authentication scheme (in my case, OIDC) Saved. Shut down container and restarted with OPENDCIM_AUTH=OIDC So I think you’re not doing it right. Container is functioning as intended. That being said, use 23.02 instead of 23.01, because it has several bug fixes in it. Scott From: Blake Sent: Friday, July 21, 2023 9:54 AM To: opendcim/openDCIM ***@***.***> Cc: Scott Milliken ***@***.***>; Mention ***@***.***> Subject: Re: [opendcim/openDCIM] Docker opendcim/opendcim 23.01 (Discussion #1395) environment: - OPENDCIM_DB_HOST=localhost - OPENDCIM_DB_PORT=3306 - OPENDCIM_DB_NAME=dcim - OPENDCIM_DB_USER=dcim - OPENDCIM_DB_PASS=Xit4PoduKid5Mifp - OPENDCIM_AUTH=LDAP - TZ=America/Chicago — Reply to this email directly, view it on GitHub <#1395 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMTY67WBTSAFEWPCBSGV2LXRKCXZANCNFSM6AAAAAA2S3M7SA> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AAMTY63JBOACXMYKU6AKAI3XRKCXZA5CNFSM6AAAAAA2S3M7SCWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAMNK2E.gif> Message ID: ***@***.*** ***@***.***> >

[coreyman2000]

Mine just go back to the login screen, :( don't see any edit , did the exact same steps ,I can see the db is populated

[samilliken]

The only way that I was able to replicate anything close to what you stated was by running the container and trying to directly interact with it. You can't do that - it needs to go through a reverse proxy with HTTPS enabled. I have changed the notes on the container from:

SSL is not enabled in the container image. It is recommended that you run through a reverse proxy, such as nginx, for providing a secure connection to the application.

To now say that it is REQUIRED to run through a reverse proxy or load balancer.

[bhoglo]

Thanks @samilliken. I was able to get into the configuration page on a fresh install of Centos 7 (without a reverse proxy). Issue is on my end, thanks for looking into it!

[coreyman2000]

What was the fix? I'm running Ubuntu and docker, and even have same issues in rocky linux

[bhoglo]

I made no changes to my configuration. I only spun up a brand new VM on Cent OS 7. Worked first try.

[samilliken]

@coreyman2000 the answer is that the container works fine. If you are not running behind a reverse proxy/loadbalancer that adds SSL, it's your setup that needs to be changed.

[coreyman2000]

thanks that was it started working right away soon as i created a ngix proxy for ssl