[JBoss JIRA] (JBIDE-19898) Error displayed on initial connection to an OpenShift Server for a new eclipse session
- First Post
- Replies
- Stats
-
Go to
- ----- 2026 -----
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2007 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2006 -----
- December
- November
- October
- September
[
https://issues.jboss.org/browse/JBIDE-19898?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-19898:
------------------------------------------
Not sure this fixes doesnt cause other problems. I now have the following behaviour:
# ASSERT: make sure that you have a basic-auth connection with stored pw listed in your
explorer
# EXEC: restart Eclipse
# ASSERT: explorer lists your connection
!existing-connection-1.png!
# EXEC: unfold it
# ASSERT: SSL Certificate dialog pops up
# EXEC: confirm the certificate
Result:
!existing-connection-2.png!
The connection dialog pops up.
The connection dialog has your connection selected in the combo (which is correct) but has
the flaw filed in JBIDE-19901: it defaults to OAuth and it wont have username/password
filled-in.
Error displayed on initial connection to an OpenShift Server for a
new eclipse session
--------------------------------------------------------------------------------------
Key: JBIDE-19898
URL: https://issues.jboss.org/browse/JBIDE-19898
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.Beta2
Reporter: Jeff Cantrill
Assignee: Jeff Cantrill
Fix For: 4.3.0.Beta2
# Create a connection to a v3 instance of openshift
# Restart Eclipse
# Open the OpenShift explorer view
# Expand the previously created connection
# Notice an error like: "system:anonymous..."
Is this related to token's not being saved? It should either go through the sequence
to establish a new token or connect.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
3966
days inactive
3966
days old
jbosstools-issues@lists.jboss.org
0 comments
1 participants
tags (0)
participants (1)
-
Andre Dietisheim (JIRA)