Casbin Forum runs on Casnode, the open-source Discourse-style forum. Try the Casnode demo →
Casbin Forum

I discovered that casvisor does not accept a self-signed certificate, only CA, I used CA and managed to open the application, now I have this problem when testing a connection but I think it has to do with the guacamole

image.png

How do I enable LDAP users to connect/create RDP access on the casvisor? I already have ldap synchronized but I don't know where to enable these permissions

image.png

Ah, I ended up sending it to the casdoor bug reports channel, I'll test it and get back to you soon, thank you

don't work, now it triggers a lot of logs, I think it's bringing the subowner and the wrong subname too, before it brought the subOwner as the organization name and subName as the username

image.png

I could be wrong in my comment above but anyway, it is triggering a lot of logs that come with the test user and still the error persists, I don't know if I should do anything else on my part

image.png

Well, the connection via ssh works normally, the problem now is the RDP connection, in addition to the security flaw going through the username and password in the application's url, it gives an authentication error when trying to log in, leaving the fields empty. Even if the password is correct, it gives the same error. To reproduce, simply create an RDP connection and leave the "username and password" fields empty

image.png

image.png

image.png

correcting, the ssh connection behaves the same way if the login and password fields are empty when adding a new access

This is along with what I said above in the images, has it been fixed or am I waiting for the issue to be closed?

1 / 45
Jul 2024