celevra

same issue here ``` documenso-documenso-1 | [next-auth][error][OAUTH_CALLBACK_HANDLER_ERROR] documenso-documenso-1 | https://next-auth.js.org/errors#oauth_callback_handler_error documenso-documenso-1 | Invalid `prisma.account.create()` invocation: documenso-documenso-1 | documenso-documenso-1 | { documenso-documenso-1 | data: { documenso-documenso-1 | provider: "oidc", documenso-documenso-1 |...

ok i'm not a next.js or prisma expert, but i've change ext_expires_in to refresh_expires_in because to comment above was ``` // Stops next-auth from crashing when dealing with AzureAD ```...

If i switch from docker to directly git compile like in the selfhosting documentation the error is gone and oidc works flawless Could be because of this: https://github.com/documenso/documenso/issues/1632

@MohdSaquib114 thank you. Nothing i can think of, if oidc is the default login method no login form is needed and also no need for the oidc button, in an...

sounds good, think you have to create a pull request. In which file do i have to put this code? than i can test it

if i compile and use it i get following error: ``` 0|documenso | Error: No session found 0|documenso | at m (/root/documenso/apps/web/.next/server/chunks/8695.js:1:52195) 0|documenso | at async b (/root/documenso/apps/web/.next/server/app/(dashboard)/documents/page.js:1:18829) { 0|documenso...

Please also support normal standards like json imap Gmail and MS also support imap...

i've created for me a simple script: ``` #!/bin/bash # export DBUS_SESSION_BUS_ADDRESS environment variable PID=$(pgrep -o gnome-shell) export DBUS_SESSION_BUS_ADDRESS=$(grep -z DBUS_SESSION_BUS_ADDRESS /proc/$PID/environ|cut -d= -f2-) /usr/bin/gsettings set org.gnome.desktop.background picture-uri `/usr/bin/curl -s...

Yes but the Data. So the gui is not open source and not hostable in a data privacy focused way? Is it the same with the Desktop client? Not working...

Awesome, will try that, thank you very much