nitnelave

Yes, trusted header is probably better. On Fri, 16 Dec 2022, 22:18 Austin Alvarado, ***@***.***> wrote: > It's probably due to the cache: loading the LLDAP page only loads static...

Related: #352

Yeah, caching can be an issue when changing versions of the frontend. To be honest, I'm not sure how that's normally handled. However, I'm surprised about the dropdown, I'll have...

I just tried debugging the dropdown issue, and it's very weird, because the component asks to be redrawn, but it's not. I don't want to report that as a bug...

Yeah, I updated the framework to a newer version hoping that it would fix this bug, but it didn't. I'm still perplexed by this.

Once #346 is submitted, can you give it a try? One thing that I wasn't sure about is how the password is managed. Currently it creates the user without a...

Sorry for the delay on the feature. Is that still something you'd like? I guess this falls under #518 , but I'm surprised we're getting `ldapmsg invalid`. Could you provide...

@shibacomputer I'm glad you're happy with LLDAP :) Could you get a packet capture of the traffic between keycloak and LLDAP with tcpdump when you get a `ldapmsg invalid` error?...

Hmm, that relates to a slightly deeper issue: the query cannot be parsed by the LDAP library we're using. To be fair, I haven't looked into the controls of the...

Looking into it, it seems to be ManageDsaIT control, which only comes into play when using referrals (AFAIU references to entries in other, connected LDAP servers), which we don't support....