By: Murillo Rocha user 12 Dec 2017 at 12:04 p.m. CST

4 Responses
Murillo Rocha gravatar
Hello everyone. Everytime we try to deactivate one of our LDAPs at: Configuration > Manage Authentication > Manage LDAP Authentication (after clicking the "Deactivate" button) we got redirected to the green page with the following message: "Oops Something wrong happened. Return to the application using below button.". Are we doing something wrong? Thank you.

By Aliaksandr Samuseu staff 12 Dec 2017 at 12:21 p.m. CST

Aliaksandr Samuseu gravatar
Hi, Murillo. Not sure if this feature still supported. We'll ask around.

By Murillo Rocha user 13 Dec 2017 at 6 a.m. CST

Murillo Rocha gravatar
Hello, Aliaksandr. Thanks for the reply. So, if I want to use two or more LDAPs for user authentication, should I use cache refresh?. Our idea were cache refreshing external LDAPs, and the ones from our organization, we would directly use LDAP Authentication (without cache refresh). We've tested adding new LDAPs in the "Manage LDAP Authentication", but until now, we haven't figured out how to properly do that. For test pourpose we tried to deactivate, but everytime we try, that error occurs.

By Aliaksandr Samuseu staff 13 Dec 2017 at 8:46 a.m. CST

Aliaksandr Samuseu gravatar
Hi, Murillo. First, regarding the initial issue: I was informed there [was a bug](https://github.com/GluuFederation/oxTrust/issues/789), it will be fixed in 3.1.2 >So, if I want to use two or more LDAPs for user authentication, should I use cache refresh? If you plan to use authentication against some backend LDAP server (instead of Gluu's own LDAP server), in almost all cases you'll need to use CR at least for initial importing of users from it. It doesn't matter how much servers you'll specify on "Manage authentication", but usually servers' layout there match the one you specify for CR. >we would directly use LDAP Authentication (without cache refresh) Gluu requires that for each user that tries to access it an internal cached entry must exist. Even if you delegate the actual authentication to some remote party, like your organization's LDAP server, there still must be a corresponding user entry in Gluu's internal LDAP server, which will store all user's attributes to release them upon request from SPs/RPs. Cache Refresh does exactly this. Overall, I would suggest to be extremely cautious when you are doing any experiments with authentication settings, as you can lock out yourself from web UI. Please create a vm snapshot, and keep admin web UI session constantly active in a separate browser so you could revert your settings.

By Murillo Rocha user 14 Dec 2017 at 7:33 a.m. CST

Murillo Rocha gravatar
Hello, Aliaksandr. Thank you for your reply and clarification. We decided to use Cache Refresh to consolidate our authentication.