[OPENAM-14092] Custom node can prevent all default nodes appearing in admin view Created: 06/Dec/18 Updated: 10/Jan/19 Resolved: 14/Dec/18
|Fix Version/s:||220.127.116.11, 6.5.1, 7.0.0|
|Reporter:||Jon Knight||Assignee:||Kajetan Hemzaczek|
|Labels:||AME, Must-Fix, TESLA|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Sprint:||2018.16 - Tin|
|Needs QA verification:||
|Are the reproduction steps defined?:||
Yes and I used the same an in the description
In some cases custom authentication nodes can cause a problem which stops all "out-of-the-box" authentication nodes appearing in the admin console.
For this particular node it seems the problem is caused by missing "public" statement on the Config object definition:
then recompile, deploy to fresh AM and all's well.
The same custom node appears to work fine with AM 5.5 and 6.0 however.
OPTIONAL - If you already investigated the code, please share your finding here (remove this text)
|Comment by James Phillpotts [ 12/Dec/18 ]|
The fix for this should be to change the PluginLifecycle class so that when each plugin installs/upgrades/registers/etc., any exception thrown does not abort the process, e.g. in PluginLifecycle.java:119:
Should be changed to:
|Comment by Peter Major [X] (Inactive) [ 12/Dec/18 ]|
Would advise against catching Throwable. At least we should rethrow it if it was an Error.
|Comment by Filip Kubáň [X] (Inactive) [ 10/Jan/19 ]|
Custom node (used the node provided in description) is present and all other nodes are visible in all trees (default and custom created)