-
Bug
-
Resolution: Done
-
Major
-
4.3.0.CR1
-
None
-
-
Workaround Exists
-
If token storage in secure storage expires and new one is required to be able to work with OpenShift 3 connection, then updating token via Edit Connection dialog does not automatically update connection. There is still error tree item under resources saying to obtain a new token.
- incorporates
-
JBIDE-21139 OpenShift 3 connection in OpenShift Explorer view is not refreshed upon editing
- Closed
- is cloned by
-
JBIDE-21881 Updating a token for OpenShift 3 connection via Edit Connection does not update resources
- Closed