Niklas Ljung

I have noticed the same behaviour using: ``` alloy, version v1.7.4 (branch: HEAD, revision: 0cad9059e) build user: root@4867b360a5cd build date: 2025-03-13T20:43:45Z go version: go1.23.5 platform: linux/amd64 tags: netgo,builtinassets,promtail_journal_enabled ``` I...

Ah, sorry, I think it must be a mistake on my part, the actual bug conserns that the run query buttons are active **for others**. I.e. if a colleague wants...

I understand the issue. For our use case we only use a read only connection so the solution is to enable two runs, but it's a bit... janky😅. However it's...

Thank you so much for your help! Yes, I saw that ticket, and it helped me realise I needed to run main and not latest release in the docker compose,...

I'm definitely no LDAP expert, but I did successfully implement SSO using ldap in a different project last week, so I just did the exact same procedure to make it...

Hmm, the debugging actually didn't add any new lines to the docker logs, did I add it in the wrong place? I just added it to the docker compose file...

I really appreciate your help in troubleshooting this issue! The only logs I get are the "standard" debug log as before. I have quadruple checked the username and password by...

A followup, I also tried binding with my own user instead of an admin account, and that also gives me a mail: ``` ldapsearch -x -H ldap://ipa.example.com -b "cn=users,cn=accounts,dc=example,dc=com" -D...

Hmm, I'm skeptical about the issue you linked, it does not seem to be related. However it couldn't hurt to upgrade the libraries, maybe some other related thing fixed it....

I've pulled the latest update, and as expected it did not help :(. Regarding the other cases, I've now tried the follow: 1. Used unencrypted ldap instead of ldaps (no...