failed/recovered LDAP server pool needs to be more prominent

oracle / opengrok

OpenGrok is a fast and usable source code search and cross reference engine, written in Java

http://oracle.github.io/opengrok/

Other

4.34k stars 745 forks source link

failed/recovered LDAP server pool needs to be more prominent #2740

Closed vladak closed 5 years ago

vladak commented 5 years ago

It happens quite often that all LDAP servers in given pool become unavailable which results in project picker to remain empty in the UI. This is confusing for the users.

One idea would be to introduce hooks that would be triggered whenever LDAP server pool fails or becomes available. The hooks would result in API call so that e.g. Message can be created/cleared which would result in error to be displayed/removed in the UI.

vladak commented 5 years ago

The trouble is that the RESTful API call needs to made from within an authorization plugin where the plugin loader constrains what classes can be loaded (as specified in the package blacklist in opengrok-indexer/src/main/java/org/opengrok/indexer/framework/PluginClassLoader.java).

vladak commented 5 years ago

The constraint is actually not about used packages rather than defined packages so this should work. It seems that Jersey API can be used.